In 30 seconds
- Detail near-term work; keep later work broad.
- Refine the plan wave by wave as you learn.
- Avoids wasted effort detailing work that will change.
How it works
Like a wave rolling toward shore, the plan comes into focus as it gets closer. Work in the next few weeks is detailed; the following months are planned as larger chunks; anything further out is a rough outline.
A simple horizon example
| Horizon | Detail level |
|---|---|
| Next 2 to 4 weeks | Refined user stories with estimates |
| Next 1 to 3 months | Features and epics |
| 3 to 12 months | Themes on the roadmap |
Why agile teams use it
A Product Backlog is naturally a rolling wave: detailed at the top, coarse at the bottom. It matches the value of responding to change over following a plan.
Myth vs reality
Myth · Rolling wave means no long-term plan.
Reality · There is one, just less detailed.
Myth · It's an agile invention.
Reality · It's also a recognized technique in traditional project management.
Myth · Distant work never gets planned.
Reality · It gets planned when it's close enough to plan well.
FAQ
How often should a wave be planned?
Often each sprint or each PI, depending on the team.
Does it work for fixed-price projects?
Yes, with scope prioritized and refined over time.
What drives the next wave?
What the team learned in the current one.