A project manager spends the first month on the software, because it feels like the biggest risk. The project is late anyway, by the exact delay of a drive unit nobody watched.
The critical path method prevents this mistake. It shows which work packages decide the end date and which ones have room.
A worked example
Seven work packages of an assembly cell, with durations in weeks and their predecessors:
- A requirements and concept, 4 weeks
- B mechanical design, 6 weeks, after A
- C electrical design, 5 weeks, after A
- D procurement of long lead parts, 12 weeks, after B
- E PLC and interface software, 10 weeks, after C
- F build and wiring, 4 weeks, after D
- G commissioning and run at rate, 3 weeks, after E and F
Two paths lead through the network. A, B, D, F, G takes 4 + 6 + 12 + 4 + 3 = 29 weeks. A, C, E, G takes 4 + 5 + 10 + 3 = 22 weeks.
The first path is critical. Every week of delay on it moves the end date by one week. The software path has 29 minus 22 = 7 weeks of float. A software delay of up to seven weeks does not move the end date.
What the example changes
The project manager now knows where to spend attention in the first weeks: design freeze and purchase orders for long lead parts. Ordering the drive units two weeks earlier gains two weeks for the whole project. Working overtime in software gains nothing.
Estimate with the owners
Durations come from the people who do the work. For uncertain packages use three points: optimistic, most likely and pessimistic. With 8, 10 and 16 weeks the estimate is (8 + 4 × 10 + 16) / 6 = 10.7 weeks.
Write down the assumptions behind each estimate. “Two engineers, full time” is part of the number.
When the date does not fit
If the calculated end is later than the date the customer needs, there are four honest options:
- Fast tracking: overlap packages on the critical path, at the risk of rework.
- Crashing: add people or money to critical packages.
- Reduce scope: deliver a variant in a second release.
- Move the date: early, with the facts of the network.
The dishonest option is to shorten durations on paper. It produces a plan that is late on the first day.
Float belongs to the project
Float is not a reserve for the owner of a package. If it is used silently, the buffer is gone when it is really needed. Report the use of float in the weekly status like a delay, and recalculate the critical path whenever a milestone moves.