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

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)

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics, Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...

4 T's - Technology, Time, Teamwork, Transparency

1) Technology: Software development technologies are the tools and methods that developers use to design, develop, test, and deploy software applications. These include a wide range of software technologies, such as programming languages, frameworks and libraries, databases, and cloud computing platforms. 2) Time: A timebox is a fixed time period within which a deliverable must be produced in a project management context. It's a time management technique that involves dividing time into individual time periods, each with its own goal, duration, and deadline. Timeboxes are self-contained calendar events that can't be extended once they've started. The fundamental principle of timeboxing is that time in timeboxes can't shift, and once the time runs out, work must stop, even if the task isn't finished. 3) Teamwork: Teamwork in project management is a measure of how well a project's team works together to achieve a goal. It involves collaboration, communication, a...

High-Tech Yuga

Search This Blog