Study guide

7.3 The Plans Practice in an Agile Context

PRINCE2 Agile Foundation Version 2

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: The Version 2 Exam & PRINCE2 Agile Essentials

1.1 About the PRINCE2 Agile Foundation (Version 2) Exam 1.2 What PRINCE2 Agile Is and How to Blend Project Management with Agile 1.3 PRINCE2 Agile Key Terms You Must Be Able to Define

2 Chapter 2: Agile and the Agile Mindset

2.1 What Agile Is, Why It Is Needed, and Agile in Projects and BAU 2.2 Being Agile vs Doing Agile, and the Benefits of Both 2.3 The Agile Mindset and the Agile Onion 2.4 The Agile Manifesto and Popular Agile Approaches

3 Chapter 3: Key Agile Concepts and Techniques

3.1 User Stories, Agile Estimation, and the Definitions of Ready and Done 3.2 MVP, Burn Charts, Workshops and Agile Events

4 Chapter 4: PRINCE2 Project Management Foundations

4.1 Projects, Project Management and the Seven Performance Targets 4.2 Project Contexts and the Five Integrated Elements 4.3 The Seven PRINCE2 Principles 4.4 Agile Scaling and Agile Transformation Success Factors

5 Chapter 5: People and Organizational Change Management

5.1 Organizational Change Management: Definition, Stakeholders and Culture 5.2 How Agile Supports Change Management and How PRINCE2 Addresses People 5.3 Project Teams, Leading Effective Teams and Communication

6 Chapter 6: PRINCE2 Agile Essentials — Principles and Practices

6.1 How the PRINCE2 Principles Support the Agile Context 6.2 The Purpose of the Seven PRINCE2 Agile Practices

7 Chapter 7: The Practices (Part 1) — Business Case, Organization, Plans

7.1 The Business Case Practice in an Agile Context 7.2 The Organization Practice in an Agile Context 7.3 The Plans Practice in an Agile Context 7.4 Plans Artifacts and Techniques: Release Maps, Timeboxes and Estimation

8 Chapter 8: The Practices (Part 2) — Quality, Risk, Issues, Progress

8.1 The Quality Practice in an Agile Context 8.2 Quality Artifacts and Techniques: Ready, Done and Continuous Testing 8.3 The Risk Practice in an Agile Context 8.4 The Issues Practice in an Agile Context 8.5 The Progress Practice in an Agile Context 8.6 Progress Artifacts and Techniques: Burn Charts and Dashboards

9 Chapter 9: The Eleven PRINCE2 Agile Roles

9.1 Directing and Managing Roles 9.2 Delivery Roles: Coaches, Product Owner, Developer and Tester

10 Chapter 10: The Processes and Their Agile Workshops

10.1 The Purpose of the Seven PRINCE2 Agile Processes 10.2 Starting up a Project and Its Agile Workshops 10.3 Directing a Project and Its Agile Workshops 10.4 Initiating a Project and Its Agile Workshops 10.5 Controlling a Stage and Its Agile Workshops 10.6 Managing Product Delivery and Its Agile Workshops 10.7 Managing a Stage Boundary and Its Agile Workshops 10.8 Closing a Project and Its Agile Workshops

11 Chapter 11: The Wider Context, AI, and Exam Preparation

11.1 PRINCE2 Agile Beyond the Project Environment 11.2 How AI Can Support PRINCE2 Agile 11.3 Version 1 to Version 2: What Changed and Common Traps 11.4 Final Review and Exam-Day Strategy

7.3 The Plans Practice in an Agile Context

Key Takeaways Explain This Topic AI

The plans practice facilitates communication and control by estimating how much work is to be delivered and when.

PRINCE2 Agile plans in layers: the project plan and release map at project level, stage plans, team plans and iteration plans.

Planning horizons differ deliberately — near work is planned in detail, distant work is planned coarsely, which is progressive elaboration rather than vagueness.

A stage is a management control period and is not the same as an iteration; a stage may contain several releases, each containing several iterations.

Plans are baselined so that progress has something to compare against, but they are expected to be refined as evidence accumulates.

Last updated: August 2026

7.3 The Plans Practice in an Agile Context

Quick summary: The plans practice facilitates communication and control by estimating how much work is to be delivered and when , and by what means. PRINCE2 Agile plans in layers — project, stage, team, iteration — with detail increasing as the horizon shortens.

Purpose

A plan is not a prediction; it is a communication and control device . It states what will be delivered, by whom, by when and at what cost, in enough detail for the relevant level of management to make decisions and to detect deviation.

That framing matters in an agile context because it answers the usual objection ("we can't plan, requirements will change"). The response is that you plan at the level of confidence you actually possess: precisely for the next iteration, coarsely for the next release, directionally for the project.

Layers of planning

Layer Horizon Owner Typical form

Project plan Whole project Project manager, approved by the board High-level products, stages, timescale, cost; the release map shows when features land

Stage plan One management stage Project manager The releases and work packages in this stage, with tolerances

Team plan One or more work packages Team manager / product owner / team coach How the team will produce its products

Iteration plan One timebox Delivery team The items pulled in and the goal for the iteration

Exception plan Replaces a plan forecast to breach tolerance Project manager, approved by the board Recovery from the current position

The release map is the artifact that links these layers. It schedules when features will be delivered, so the board can see which capability lands in which release and therefore when each benefit starts to accrue.

Stages, releases and iterations

This distinction generates exam questions every sitting.

A stage is a management control period . It exists so that the project board can make a go/no-go decision at its boundary. Stage length is chosen for management reasons — risk, investment size, decision points — not for delivery cadence.

A release is a set of features delivered together into use.

An iteration (or timebox, or sprint) is a delivery cadence , typically one to four weeks.

They nest: a stage contains one or more releases; a release contains one or more iterations.

A stage is not a sprint. Treating them as equivalent produces one of two errors: board decisions every two weeks, which is unworkable, or no meaningful control points at all.

Progressive elaboration

Planning horizons differ deliberately:

The next iteration is planned in detail: specific stories, estimated, meeting the Definition of Ready.

The current release is planned at feature level: which capability, in roughly what order, at what confidence.

The rest of the project is planned at epic level: what capability areas exist, sized in t-shirts, sequenced by benefit.

This is progressive elaboration , not vagueness. The distant plan exists and is testable; it is simply expressed at the resolution the available evidence supports. Elaborating distant work in false detail is waste, because the detail will be invalidated before it is used.

Planning activities

The PRINCE2 Agile planning approach runs through a recognisable set of activities. Those the exam refers to include:

Preparing estimates — sizing the work, using relative estimation such as story points or t-shirt sizing.

Preparing the budget — converting effort and duration into cost, including risk and change budgets.

Organizing work packages — grouping products into packages that can be agreed with a delivery team, each with its tolerances and its Definition of Done.

Documenting the plan — recording the agreed plan, and this is the activity in which the release map is updated .

Alongside these sit the product-focused steps PRINCE2 has always used: defining and analysing the products, identifying activities and dependencies, and analysing the risks in the plan.

What tailoring looks like

Estimation is relative rather than in absolute hours, and forecasting uses velocity once a team has history.

Plans are living. They are baselined so deviation can be detected, but re-planning at the end of each iteration is normal rather than exceptional.

Scope is expressed as prioritized backlog items , so the plan naturally contains the flexibility that time-and-cost-firm delivery requires.

Detail is deferred, not omitted. Deferring the detail of low-priority items is progressive elaboration; failing to define what the project delivers overall is a breach of focus on products .

Team plans are made by the team. The project manager agrees the work package and its tolerances; how the team meets it is the team's decision.

The relationship with progress

Plans and progress are a pair. Plans set the baseline; progress compares what has been delivered with what was planned and controls deviations that would cause an exception. If a question mentions estimating and scheduling, it is plans; if it mentions comparing delivery against plan, it is progress.