
Project & Schedule Management · Module 3 of 4
Buffer the Schedule: Where Safety Time Belongs
The last two modules found Cedarline's critical path and paid to shorten it — both pretending durations were known. This one drops the pretense. The catalog runs again with uncertain task times, and you must commit to a launch date and place a fixed pool of schedule buffer to protect it. Two traps fire at once. The most-likely estimate is biased low: work is right-skewed, so the copy task's most-likely of 8 days has an expected time of 11 and a tail to 32 — plan to 8 and you're late more than half the time. And the longest chain isn't the riskiest: the production chain is critical by average (mean 12) but predictable (spread 1), while the shorter copy chain (mean 11) is wild (spread 5), and it is the one that blows the deadline. Classic PERT reads only the critical path and reports 98% on-time; because both chains must make the merge, the truth is 71% — a 27-point lie of omission. Then you distribute six buffer-days and see the payoff: pour them onto the critical production chain and the gauge barely twitches (71% to 73%); pool them on the wild copy chain and it climbs to 94%. The lesson is to pool the buffer where the variance lives, not where the length is — plus the aggregation insight (one buffer of the root-sum-of-squares beats padding every task) and a replay where a new printer flips the variance and the buffer must move. The chain worth protecting isn't the longest one — it's the most uncertain.
0 of 20 items completed0%~80 min remaining
Material · 20 items