Rolling Wave Planning
Rolling wave planning details near-term work finely while leaving far-term work coarse, decomposing each block as its start approaches.
How the technique works
Near-term work is decomposed finely; far-term work stays coarse. Work starting within the next two or three months gets broken down to Work Package level with dates and owners, while work half a year out remains a single higher-level block. As the wave approaches, that block is decomposed in turn. The trigger is usually a phase transition — once design ends and the shape of implementation is clear, the next wave gets its detailed plan. The key point: what is deferred is decomposition, not scope. Even distant work must have its place in the WBS.
Why it matters
A detailed plan made without information is just a precise-looking guess. Break down month-six work into daily tasks at project start, and within weeks that plan diverges from reality, leaving only the cost of maintaining it. Rolling wave planning defers detail to the moment information exists, managing plan accuracy and planning cost together. It is especially useful in the middle ground between predictive and agile delivery: fix total scope with the WBS, then fill in detailed schedules wave by wave, and you get the benefits of both.
Common misconceptions
The biggest one is reading it as "plan later." Rolling wave planning is not a license to defer scope definition — it adjusts when you decompose, not whether. Distant work still needs its deliverables and rough size fixed early, or estimates and the overall schedule cannot stand. The opposite failure exists too: leave a vague block untouched with no re-decomposition date, and one day the whole block becomes imminent work at once. Scheduling the re-decomposition for each wave in advance is the safe habit.
In wbsgantt the WBS tree can be extended with deeper decomposition later, and weights redistribute automatically to keep sibling sums at 100 as new children arrive — a natural fit for widening the tree wave by wave.