• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Practice : Rolling Wave Planning

Purpose and Strategic Importance

Rolling Wave Planning enables teams and organisations to plan with precision where it’s needed and flexibility where it’s not. It balances long-term vision with short-term adaptability by progressively detailing work as it approaches implementation.

This practice helps reduce waste from early over-specification, enables faster response to change, and creates space for discovery. It supports evidence-led decision-making, improves stakeholder confidence, and maintains momentum without rigid commitments.


Description of the Practice

  • Plans are created at varying levels of detail: high-level for long-term horizons, detailed for near-term delivery.
  • The immediate "planning horizon" (e.g. 1–2 sprints ahead) is shaped with clarity and commitment.
  • Mid- to long-term work is kept intentionally coarse and updated regularly as understanding evolves.
  • Planning cadence is synchronised with product cycles, customer needs, and team rhythms.
  • Teams adapt plans based on learning from delivery, feedback, and environmental changes.

How to Practise It (Playbook)

1. Getting Started

  • Define appropriate horizons (e.g. now, next, later) for roadmap and backlog views.
  • Clarify that near-term work should be ready for sprint planning, while longer-term items are placeholders for intent.
  • Engage stakeholders in roadmap shaping while managing expectations about certainty.
  • Use tools like roadmap boards, opportunity canvases, or OKR alignment maps.

2. Scaling and Maturing

  • Introduce planning cadences (e.g. quarterly framing, monthly shaping, fortnightly sprint planning).
  • Incorporate feedback loops to regularly revise future plans based on what is learned.
  • Use discovery work to reduce uncertainty in future waves.
  • Ensure dependencies, risks, and experiments are surfaced early—but detailed only when necessary.

3. Team Behaviours to Encourage

  • Revisit and refine plans regularly—treat them as living artefacts.
  • Ask “What do we need to know next?” instead of “What will we do months from now?”
  • Shape upcoming work collaboratively and iteratively.
  • Communicate uncertainty with confidence, not avoidance.

4. Watch Out For…

  • Overplanning far in advance, leading to waste and rework.
  • Underspecifying near-term work, creating delivery confusion.
  • Treating roadmaps as fixed commitments rather than directional tools.
  • Misalignment between discovery pace and planning rhythm.

5. Signals of Success

  • The backlog reflects the right level of clarity at the right time.
  • Teams feel prepared for the near term and unburdened by distant speculation.
  • Stakeholders see direction without demanding fixed dates for everything.
  • Roadmaps and delivery outcomes are increasingly aligned.
  • Teams adapt plans confidently and transparently as they learn.
Associated Standards
  • Overplanning is avoided through progressive elaboration
  • Backlogs are prioritised based on measurable business value

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering