Tuesday, April 6, 2010

The importance of short lead times in multi project environments

Multi project environments resemble industrial manufacturing in many ways. One resemblance is that planning generally is about finding the best balance between short lead time and high utilization of critical resources.

We define the lead time is the period from start of a project (or part) to completion.

Our advice is to aim for as short project lead time as possible because it results in so many positive things:

  1. Quicker benefits. A project will normally be decided to improve something; there will be a cost of the project and a projected benefit. Therefore the sooner the completion the earlier the benefits will be obtained.
  2. Less money in the works. During project time cost will be incurred and an investment is made. The longer the period the more accumulated money is spent. Money which comes at a price, normally interest or risk of default on payments.
  3. Less wasted time on starting up again. Whenever people have to change to other tasks during a day the more time risk being wasted because the person has to reorient himself and get up to speed again.
  4. Effective dynamic coordination. Generally it is believed that putting pressure on lead time makes people become more responsible and inventive in solving not foreseen disruptions. By lowering the sea level the rocks appear so you can navigate around them.

You may ask: Are there no disadvantages? I can think of none other than overdoing it. Overdoing it can cause trouble with workload for bottleneck resources and there must be some flexibility in the project plan to swallow the unforeseen, if the plans are too tight, the slightest disturbance can create ripple effects,

There are a number of ways lead time can be shortened if you have good knowledge about your project content and the resource requirements. And this is really the challenge: Careful project design. The more a new project resembles other earlier projects, the better the possibility is for gathering experience and utilizing it in the planning for new projects.

You should think about:

  1. Parallel processing. Look to see where there no interdependencies and make parallel branches in the work break down structure (WBS).
  2. Within the same branch find where you can permit overlapping, i.e. an activity can be started before the previous activity has ended.
  3. Where you can speed up an activity by assigning more resource capacity, e.g. more people, of course without adding too much extra cost for coordination and/or having resources spending all their time for a period on that particular activity.

Again the devil is often to be found in the resources and their capacity. If two activities which theoretically could run in parallel use the same critical resource (which perhaps already is overloaded) it will of course not be possible.

Shortening of lead times is based on resource management.

4 Responses to “The importance of short lead times in multi project environments”

Several interesting replies came in via a discussion on this topic on LinkedIn, check it out here: http://www.linkedin.com/answers/business-operations/project-management/OPS_PRJ/669378-16678054

thanks for all those who read this and gave such interesting and useful feedback!

Anonymous said...

I wish you hadn't closed the question on LinkedIn, as there were several interesting points made.

The definition of "lead time" depends very much on your point of view. From the point of view of the customer, lead time is the time from when I sign the contract to when I get delivery. Then you have the internal view: usually the time from start to finish. If you have a real multi-project environment, you can start talking about cycle time which looks at finish-to-finish timing of projects.

All your tips above sound like tips related to single projects: basically checking assumptions built into the project network. All good suggestions.

But in a multi-project environment where people working on one project are involved in other projects as well, then you need mechanisms that help executing all these projects. As with others that mentioned resource management, that is an important aspect. But I also believe that the way management run projects needs to be addressed: don't force people to multi-task; help people focus; ask them how much more time they need to finish the task; ask them what is getting in their way; track the frequent causes of delay (so you can eliminate them);...

One mechanism for addressing this is Critical Chain Project Management, which comes out of the Theory of Constraints community.

Hi Jack,

I'm a bit new to LinkedIn - my apologies for closing the topic too soon! I think you bring good points and I would like to learn more about the Theory of Constraints community, I'll check that out!

Thanks,

Vanessa

Anonymous said...

There are a couple TOC-related groups on LinkedIn where there are some active discussions running. In addition there is a great YahooGroup on Critical Chain Project Management that might be helpful directly - http://groups.yahoo.com/group/CriticalChain/

Leave a Reply