Progressive Elaboration

What the principle says

Plans are not completed in one pass — they are refined iteratively as information accumulates. A one-line charter summary becomes a scope statement, the scope statement becomes a WBS, and the WBS's coarse blocks become Work Packages with schedules. Each pass happens at a moment with more information than the last, so each is more precise. Rolling Wave Planning is the best-known application of this principle to scheduling: if progressive elaboration is the principle, rolling wave is one way of executing it.

Why it matters

It turns early-plan uncertainty from a defect into a premise. Organizations that reject the principle demand a perfect plan at kickoff, and teams fill in the unknowns by pretending to know. The result looks precise but is a number without a confidence interval. Accept progressive elaboration and the response changes: fix the large structure and rough sizes early, then design elaboration points into the schedule itself so each phase's deliverables feed the next phase's plan. Plan revision stops being evidence of failure and becomes a scheduled procedure.

Common misconceptions

Confusing it with scope creep is the dangerous one. Progressive elaboration raises the level of detail within approved scope; scope creep grows the scope itself without approval. When someone says "the work grew as we elaborated," ask which happened. If what grew is the list of detail items, that is elaboration; if what grew is the set of deliverables, that is creep — and it must go through the baseline and change procedure. Blur this distinction and scope grows quietly under the name of elaboration.