Placing Projects on Hold

In a recent article titled 'Put it in park, then drive' Jack Vinson discusses the potential benefits to project driven organizations of placing certain projects on hold. This seems like a fairly obvious solution but in reality there are potential pitfalls. Primarily, it's likely you've established some sort of deadline with a client, so placing their project on hold may present a problem.

I know that in my world, it would be ideal to be able to work on one project until it was complete. There have been some occasions that we've had the luxury of doing this and the overall product generally ends up being better. Not to mention the resources required to finish the project are usually less than if the project is just one of many.

How could there ever be too many projects in progress? The main problem, which Jack alludes to, is that there always needs to be some 'work in the pipeline' to keep the operation running. If you were to work on one project at a time from start to finish and then start looking for the next project the likelihood is high that you would have gaps in production where people are not doing anything but waiting for the next project.

There is also the issue of having staff that work on different components of a project. If you have a project that requires X, Y, Z from your services it's hard to keep all of the people working on each of those components busy at the same time. The result is that you end up taking a new project on because the 'X' group needs work even though the 'Y' and 'Z' groups are overloaded.

I feel the real solution to being able to keep project oriented staff busy and maintain a decent backlog of work is to be able to accurately schedule resources. If you can do this successfully and communicate the situation up front to your clients you'll allow ample time to give projects the attention they need and hopefully avoid having to park a project once it is started.