Skip to main content

Horizon planning Agile Pgm

📘 Horizon Planning in Agile PgM

Horizon Planning in Agile Programme Management is a way of planning at different levels of detail over time, accepting uncertainty and enabling change—while still maintaining control and alignment to the programme vision.

In simple terms:

> Plan in detail only what is near, and keep the future flexible.




---

🔭 The Three Horizons (most commonly used)

Horizon 1 – Near Term (Detailed Planning)

Covers short-term delivery

High level of certainty

Capabilities to be enabled soon

Detailed planning is appropriate

Projects and tranches are clearly defined


👉 “Only those capabilities to be enabled in the short term can be planned in detail.”


---

Horizon 2 – Medium Term (Outline Planning)

Covers upcoming capabilities

Moderate uncertainty

Planned at high level

Priorities may change based on:

Early benefits realised

Lessons learned

Changes in business strategy



👉 Focus is on options, sequencing, and dependencies, not detail.


---

Horizon 3 – Long Term (Vision-Level Planning)

Covers future direction

High uncertainty

No detailed planning

Driven by:

Programme vision

Business strategy

Expected benefits



👉 Acts as a strategic intent, not a commitment.


---

🎯 Why Horizon Planning is used in Agile PgM

Horizon planning helps to:

Deliver benefits incrementally and early

React to changes in business environment

Avoid over-planning and waste

Maintain continuous alignment to business strategy

Balance control and agility



---

🧠 Exam-ready one-liner

> Horizon planning in Agile PgM plans near-term work in detail, mid-term at high level, and long-term at vision level, enabling early benefits while remaining adaptable to change.




---

🔑 Key takeaway to remember

Near = Detail

Mid = Outline

Far = Vision



Comments