Planning Horizons: Short Rolling Plans vs Full Project Baseline
Compare short rolling plans and full project baseline approaches to project planning and understand how each manages uncertainty, flexibility and control.
How far ahead should a project plan in detail? The answer depends on how much you actually know — and how much is likely to change. Planning too far ahead in detail creates false confidence and bureaucratic waste; planning too short-term leaves the project without direction and makes governance difficult.
The Options
Short Rolling Wave Planning
Planning in detail only for the near term (typically 2–6 weeks ahead), with progressively less detail for later phases. The plan is updated at each planning cycle as more information becomes available. This approach is natural in Agile and hybrid environments, and is particularly effective when requirements are uncertain or the environment is volatile. It accepts that detailed long-range plans will be wrong and invests planning effort where it has the most value.
Full Project Baseline
Developing a comprehensive, detailed project schedule from initiation to completion before work begins. This provides a clear baseline against which performance can be measured, supports formal change control and is required by most traditional governance frameworks. It works best when scope is well understood, dependencies are clear and the project environment is relatively stable.
Phased Baseline
A middle path: developing a detailed baseline for the current phase and a high-level outline for future phases, with detailed planning of each subsequent phase before it begins. This approach reduces the planning effort invested in uncertain future work whilst maintaining sufficient governance structure for decision-making and investment approval.
Why It Matters in Practice
Earned Value Management (EVM) — the dominant approach for large programme performance measurement — requires a full baseline to function. Defence, construction and infrastructure projects typically mandate this. In contrast, digital transformation and product development programmes increasingly favour rolling wave approaches that acknowledge the inherent uncertainty of innovation work.
The failure to match planning horizon to project type is a common source of waste: large IT projects with full baselines that become outdated within weeks, or agile teams without enough forward visibility to manage dependencies between squads.
In the Simulation
In SPPIN Sim, your planning horizon choice affects your schedule performance score, your change management cost and your forecasting accuracy metric. Full baseline planning scores well when the project unfolds as expected but absorbs large schedule penalties when scope change events occur. Rolling wave planning adapts more gracefully to change events but can score lower on baseline adherence metrics in stable turns.