Rolling Wave Planning

Long projects and programs face a basic planning problem: the further ahead a plan looks, the less certain it becomes. Requirements change, early work reveals new information, and assumptions about people and technology turn out to be wrong. Trying to plan everything in detail at the start produces plans that look precise but are largely guesswork, and that need constant rework. They can also create false confidence, since a detailed plan for work two years away suggests more certainty than anyone has. Rolling wave planning accepts this uncertainty. It plans the next phase, or wave, in detail, keeps later phases at the level of milestones and estimates, and adds detail to each wave as it approaches.

The technique is recognized in project management standards and is widely used in large programs, research and development, and any work where later phases depend on what is learned earlier. It has much in common with agile planning, which also plans in short cycles. For portfolio leaders and PMOs, rolling wave planning offers a way to keep plans realistic, to fund work in stages and to review progress and direction at regular intervals.

Definition of Rolling Wave Planning

Rolling wave planning is an iterative form of progressive elaboration in which the work to be done in the near term is planned at a detailed level, while work further in the future is planned at a summary level and refined as the project progresses.

It is often used alongside a phased project lifecycle and incremental funding, and it supports approaches such as agile portfolio management that plan in short cycles.

How Rolling Wave Planning Works

The project is divided into waves, often aligned with phases, quarters or major milestones.

The current wave is planned in detail, with specific tasks, assignments, durations and costs. This detailed plan becomes the baseline against which progress is measured during the wave.

Later waves are planned at a summary level, often as planning packages with estimated effort, cost and milestones but no detailed tasks.

Before each new wave begins, the team plans it in detail using what has been learned so far, and updates estimates for the waves that remain.

Throughout, the overall objectives, major milestones and budget remain visible, so the project keeps a clear direction even as the detail changes.

Planning Horizons

Detailed plans typically cover the next one to three months, depending on how stable the work is.

Summary plans cover the rest of the current phase or year, with milestones and resource estimates.

High-level plans cover the remainder of the project, with major phases, outcomes and budget ranges.

The right horizon depends on the work. Stable, well-understood work can be planned further ahead, while exploratory work needs shorter waves.

Importance of Rolling Wave Planning in Strategic Portfolio Management

Rolling wave planning keeps plans realistic. Detailed plans are made when there is enough information to make them accurate, reducing wasted planning effort and rework.

It supports learning. Each wave incorporates what was learned in the previous one, so the project adapts rather than following a plan that no longer fits.

It also creates natural review points. The transition between waves is a good time for sponsors and portfolio leaders to confirm that the project should continue and in what form.

Rolling Wave Planning and Financial Management

Rolling wave planning fits well with incremental funding, where money is released one wave at a time based on progress and updated estimates.

Budgets for later waves are held as estimates with ranges, which gives finance a realistic view of uncertainty rather than false precision.

Updated estimates at each wave give finance teams better forecasts of total cost and timing, improving portfolio and capital allocation decisions.

When used with earned value management, planning packages for later waves hold budget at summary level until they are converted into detailed work packages.

Common Challenges

Sponsors and finance teams may want a detailed plan and fixed budget for the whole project at the start, which rolling wave planning does not provide.

Teams can use the approach as an excuse to avoid thinking ahead, leaving later waves too vague to support resource or budget planning.

Frequent replanning takes effort and can create confusion if changes are not communicated clearly to stakeholders. A short summary of what changed at each wave, and why, helps keep everyone aligned.