≡ Menu
Pawel Brodzinski on Software Project Management

Why Small Projects Are Great Lesson for Project Managers

What is the biggest difference between a small and a big project from PM perspective? In short: there’s less typical projects management job. Schedules are smaller, stakeholders are easier to manage, requirements are limited, complexity isn’t anywhere close to a number one issue, control and supervision are less time consuming etc. Basically a project manager should have more time.

On the other hand problems which have to be resolved are similar. Changing business requirements, poor estimates, slips, lack of stakeholder engagement, changing priorities, you name it.

You could say that PM does everything they’d do in a big project but doses are smaller. This means they have more time to spend on… on what? If they’re not a kind which will use all available time for surfing through the internet to learn which celebrity sleeps with whom they’ll probably take the effort of making several steps deeper into the project. They’ll learn more technical details and analyze business features better. They’ll do by themselves some work typically assigned to different subject matter experts. Maybe testing, maybe documentation or maybe analysis. Either way they’ll learn more about the project than they’d do if it was a big complex beast which draws all the PM’s attention just to keep it on the track.

This is exactly why a small project is a great lesson. If you learn more about the project you can analyze better what was done well and what went wrong. You’re able to verify more things by yourself, no matter whether you talk about project, project team actions or your performance. You also have less external constraints which you have to align with so there’s more freedom when it comes to decision making.

You just won’t do much experimenting in this huge super-duper project a company has won last month. But you definitely would think about it in that small 6-week project you’re going to do with just a few people.

in: project management

9 comments… add one

  • Andrew Meyer August 4, 2009, 8:02 pm


    isn't there also the question of how much infrastructure is necessary? With a small project, minimal infrastructure (project schedules, meetings, communication plans etc.) The larger the project, the more infrastructure is needed. At some point the law of declining returns sets in, the infrastructure needed for the project exceeds the project.

    I believe Einstein said something like "Everything needs to be reduced to its simplest form, but no simpler." Likewise, a project needs to be as small as it can possibly be, but no smaller.

    Is that what you're trying to get at?


  • Josh August 4, 2009, 9:38 pm

    This is very true Pawel. I'd say that big projects are also a great lesson for project managers.

    The dynamics are completely different, and very important in both cases.

    On the last project I worked on, politics was more important. Communication, dealing with multiple stakeholders and multiple project managers that worked for me, these all made things much more complex.

    I had a scheduler, risk manager, project controller, etc. At times, I longed for my smaller projects where I could do these things myself.

    Every project can be a great lesson, if you let it be.

    Josh Nankivel

  • project management August 5, 2009, 2:44 am

    From budget constraints to unrealistic expectations, small projects can also be very difficult to manage. So such challenging projects and difficult clients can make a software project manager’s job quite stressful.
    We addressed this issue in our recent article Small Projects Management: 7 Tactics That Pay-Off Big.

  • Pawel Brodzinski August 5, 2009, 2:57 am


    Simplicity plays its role on every front. And yes, I definitely forgot about infrastructure.

    What I'm trying to get at is the simpler is the project the more merits can be touched by a PM. And that's great since we're often put somewhere high where we no longer do "the real work" but coordinating group of people.

  • Pawel Brodzinski August 5, 2009, 3:01 am


    Of course big projects are a valuable lesson too but a different one. As you say you can have a project where the most important task is dealing with office politics (which sucks if you ask me).

    And of course experienced PM should be able to deal with all sorts of environments.

    I just had this thought before writing the article that we tend to focus on this big complex projects as these are ones which look difficult. Then we expect to learn. At the same time we tend to leave small projects with a "simple task" label which is wrong. Or so I believe.

    Actually every project can be, and should be, a lesson. Especially these which doesn't go according to plans.

  • Poorav Sheth August 6, 2009, 5:29 am

    One thing that needs to be considered here is what you mean by a "small" project. A 10 man-month project could involve 2 resources for 5 months or it could be 5 resources working for 2 months. With the former, I agree that the PM would have more time to get involved in other activities and to experiment a bit. If it is the latter, the PM will have to crunch all the project management activities (although less complex) in a short duration of 2 months. This will leave him with no time.
    In short, duration of the project should also be considered before a PM labels a project as small and starts planning for things to do in his free time.

  • Pawel Brodzinski August 6, 2009, 5:38 am


    Actually I used an ambiguous term "small" on purpose. You can have 10-man-month project which will be small as it's relatively easy, tasks are well-defined and there isn't much of bureaucracy around and at the same time you can have a two-man-month project which is a hell of a PM since you have 4 subcontractors, tons of different documentations to to process and strict process constraints which makes it rather a complex project.

    Judging by the length of a schedule only it's hard to say whether project is "small" or not. On this point – fully agree.

  • Poorav sheth August 6, 2009, 6:25 am


    I agree, it would be a combination of factors such as effort, duration, team size, complexity, process confirmance etc. that would help determine if a project is "small" or not.

    I used to work at an Offshore Provider that had startups as clients and they would typically have projects similar to the 2 man-month project that you have described. It was an uphill task to try and convince the client to pay for a vendor-side PM. Their thinking was this is a "small" project so why should I pay for the "overhead" of a PM. Big mistake! Ultimately, we used to "invest" in a part-time PM to ensure that the project was managed successfully till the end and it paid off.

    What has been your experience with such clients?

  • Pawel Brodzinski August 6, 2009, 11:48 pm


    Actually no matter whether a client pays for a PM in the team or not there are some project management tasks which have to done. Sometimes you don't even need dedicated PM (as it in my team now) because a project isn't complex enough to require full-time project management job. But we still need project plans, schedules, a little bit of formal communication with customers, some coordination with other teams in our company etc. It is project management and it is being done.

    The other thing is whether and how client pays for the job. Majority of projects I worked on were fixed-price not time-and-material and, as such, we rarely needed to ascribe each hour of our project managers to project costs.

    However if you set up an agreement where you list each resource working for a client and they reject to accept a PM there, well, you can always treat it as a supportive role for developer (which it really is) and include it somehow in your margin. After all you don't add a secretary to the list of resources and she helps your team, isn't she?

Leave a Comment