Rolling Wave Planning

Definition

Rolling wave planning is a progressive elaboration technique where work in the near horizon (the next 4–12 weeks, depending on project type) is planned in detail, while later work is held at summary or milestone level until enough information exists to plan it properly. Every planning cycle, the detailed window rolls forward. The technique is recognised in the PMBOK and is widely used on EPC, infrastructure, and large IT programmes — projects where committing detail too early produces fiction, not plans.

Why It Matters

Early in my career I built a 4,800-activity P6 schedule for a 36-month industrial project at award. Six months in, half the activity dates were wrong because the design hadn't matured. We spent 30 hours a week maintaining the schedule and produced numbers nobody trusted. The next project, we used rolling wave: the first three months detailed, the remainder at level 2/3. Schedule maintenance dropped to 6 hours a week. Trust in the dates went up, not down — because the detail we did publish was real.

How It Works

• Tier 1 — detailed window: the next 4–12 weeks at activity level (1–5 day durations), fully logic-linked, resource-loaded.
• Tier 2 — known window: months 2–6 at work-package level, key milestones fixed.
• Tier 3 — strategic window: beyond month 6 at summary level — phases, gates, milestones.
• Roll forward: every planning cycle (typically monthly on construction, every sprint or two on IT), the Tier 1 window slides forward and another month of Tier 2 work is elaborated to Tier 1 detail.

Real-World Construction Example

A 480MW combined-cycle plant ran a three-tier rolling wave for its 28-month construction phase. The 12-week look-ahead held 600–800 detailed activities; the next six months held 1,200 work-package-level activities; the remainder was held in 40 summary bars. The integrated master schedule had under 3,000 activities — a fraction of what a "build it all in detail" approach would have produced — and the schedule was demonstrably more accurate at every monthly update.

Real-World IT Example

A SaaS company running a 9-month platform replatform used rolling wave alongside agile delivery. The next two sprints were fully estimated and assigned; sprints 3–6 had stories sized but not assigned; sprints 7+ existed only as themed quarterly objectives. Stakeholders had a credible roadmap; the team had a planning load that didn't crush them. When market priorities shifted at month 4, only Tier 2 and Tier 3 needed reshaping — Tier 1 kept executing.

Practical Lessons Learned

• Match the wave length to the project's information half-life. Construction often runs 90-day detail; software runs 2–4 sprint detail.
• Tier 2 must have enough structure to forecast. Pure summary bars destroy forecast credibility.
• Discipline the elaboration. If month 4 work doesn't elaborate to Tier 1 detail by the end of month 3, something is wrong upstream.
• Pair it with Last Planner. The 6-week look-ahead and weekly work plan are rolling wave in action.

Common Mistakes

• Tier 3 too vague. "Phase 2 — 12 months" is not a plan; even strategic-level work needs date-anchored milestones.
• Tier 1 too short. A 2-week detailed window leaves no time for procurement or risk to surface.
• Never elaborating. Some teams plan the first wave and then forget to roll it; six months in, Tier 1 has shrunk to nothing.
• Calling it "rolling wave" to hide a missing plan. The technique requires structure at every tier, not absence at later tiers.
• Inconsistent activity coding. Activities migrating from Tier 2 to Tier 1 must keep their WBS coding or the variance reporting breaks.
• Failing to baseline each wave. Baseline once at project start and update only the live waves; without that, you can't measure schedule performance.

Expert Tips

• Codify the wave horizons in the schedule management plan. Make them contractual, not discretionary.
• Hold an elaboration workshop monthly. Walk the Tier 2 work that's about to elaborate; ensure ownership and inputs are ready.
• Communicate the technique to executives. They sometimes mistake summary-level later work for "we don't know what we're doing" — they need to understand why detail at month 18 is harmful, not helpful.
• Audit elaboration quality. Newly detailed waves should hold up against the standard activity-quality checks (durations, logic, resources).
• Use the schedule health checker on PMMilestone.org on each new wave.

Key Takeaways

• Rolling wave plans detail near-term work and summarise later work, then progressively elaborate.
• It produces more accurate, more trustworthy schedules than full-detail-at-award approaches.
• Works on construction, EPC, infrastructure, and large IT programmes alike.
• Requires discipline in elaboration cadence and consistent WBS coding across tiers.
• Pairs naturally with Last Planner, look-ahead planning, and agile sprint cadence.

Related Encyclopedia Entries

• Look-Ahead Schedule
• Last Planner System
• Baseline Schedule
• Integrated Master Schedule
• Work Breakdown Structure
• Agile Project Management

Related Research Articles, Case Studies & Tools

• Schedule Health Checker
• Project Controls Academy
• Learning Tracks
• Books & Publications
• CCGT rolling-wave case study
• Progressive elaboration research notes