Collective Wisdom from the Experts 83
For example, on a 40-day total duration for a design phase, add 4 days of buf-
fer time to the end of the phase, for a total phase duration of 44 days. Will the
phase actually take 44 days? Perhaps not, but the “unused” time can then be
either carried forward or added to future buffers.
As experienced software project managers know, projects may proceed on
schedule during the early stages, only to end up dragging on later in the
process. Getting ahead of the curve almost always has more advantages than
disadvantages.
Expect skepticism the first time you try this approach. “Nonproductive” time
is the first thing managers will want to eliminate when they review your sched-
ule. Stand your ground. Make the simple point that you are performing basic
schedule risk management.
If you have a phase of the project that is riskier than another, add more buffer
at that point. You may be able to add less of a risk buffer in other spots on the
timeline.
Last, make sure that you are not “double-dipping.” Double-dipping would be
adding extra time at the task level and then again at the phase level. The tech-
nique works best when you are not already buffering each of your task dura-
tions by routinely adding extra time to each activity to deal with the unknown.
Try it. It works!