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



Labels:

Comments

Post a Comment

Popular posts from this blog

Certified Enterprise Architect Professional (CEAP) - Module 5 - Architecture Frameworks

Architecture Frameworks: An Architecture Framework is a theoretical structure that has the purpose of developing, executing, and maintaining an Enterprise Architecture. Advantages of EA framework: Simplify Breaks down areas of the business process Organise business components and create and identify relationships between business Determine the scope Customization in the existing framework Disadvantages of EA framework: Need to follow process Provides only direction and not information It's based on goal and objective Need creativity and proactive thinking Zachman Framework: The Zachman Framework is a widely used model in Enterprise Architecture (EA) that provides a structured way to classify and organize an organization's information infrastructure by defining different perspectives from various stakeholders, allowing for a holistic view of the enterprise and facilitating alignment between business needs and technology solutions; essentially acting as a template to organize arc...
Post a Comment
Read more

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a " stand-up meeting ". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other: • What did I accomplish yesterday?  • What will I do today?  • What obstacles are impeding my progress?  Some people are talkative and tend to wander off into Story Telling .  Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted. These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting.  Here are few tips for running a smooth daily meeting:  • Everyone should literally stand-up and no one should sit down ...
Post a Comment
Read more

Certified Enterprise Architect Professional (CEAP) - Module 4 - Architecture Precursors

 Architecture Precursors: Precursors to modern Enterprise Architecture (EA) include early frameworks like IBM's Business Systems Planning (BSP), which focused on aligning business strategy with information systems, as well as other Information Systems (IS) architecture methodologies that emerged in the 1970s and 80s, emphasizing the connection between business processes and IT systems, laying the groundwork for the holistic view of an organization that EA represents today; the "Master Plan for Information Systems" by Evans and Hague is also considered a foundational concept in this area. Drivers: internal / external pressure enforce to change the system Aims & Directives: Aims:  Goals Objectives Requirements Directives: Principles (example: Principles can be associated with business, data, applications, infrastructure, or security) Policies (example: Members of the public have minimal access to data) Business Rules (example: A rule directs and restricts a procedure)
Post a Comment
Read more