Rolling-Wave Planning: Continuous Roadmap Updates Instead of Big Upfront Planning

Definition

Rolling-wave planning is a discipline of updating the product roadmap and feature-set backlogs on a regular cadence—typically after every iteration or when teams complete features—rather than planning comprehensively before the program starts. The practice separates detailed planning (specific stories for the current quarter) from directional planning (broad themes and epics for the next 2–3 quarters). As feature teams deliver, the product owner updates the roadmap based on what has been learned, completing features that were not anticipated, and deferring or eliminating features that no longer add value.

In the Book

Rothman distinguishes the big-picture roadmap (showing product direction and themes) from the quarterly roadmap (showing which feature sets and stories are in scope for each internal release). She recommends avoiding detailed planning for more than one quarter ahead, and updating the roadmap after every iteration or every few completed features. Themes evolve into feature sets; feature sets evolve into stories. This rolling approach avoids the trap of planning stories for months in advance only to discover the assumptions were wrong.

The book emphasizes that roadmap plans that assume fixed scope and fixed schedule fail in practice. Rolling-wave planning acknowledges that learning happens as teams work, and that the organization's priorities may shift. By planning in waves (high detail near-term, low detail far-term), teams can commit to near-term deliverables while remaining responsive to change, without having to do massive re-planning cycles.

Why It Matters

Rolling-wave planning solves the program-level problem of uncertainty at scale. Larger efforts cannot reliably predict what will take how long, what dependencies will emerge, or what the market will want by the time a feature ships. Planning the whole thing upfront creates a false sense of control that leads to either aggressive over-committing or defensively padding estimates so much that delivery becomes slow. Rolling-wave planning acknowledges the reality: teams learn as they work, and the roadmap must evolve with that learning, without losing strategic direction.