Study guide
1.3 PRINCE2 Agile Key Terms You Must Be Able to Define
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
1.3 PRINCE2 Agile Key Terms You Must Be Able to Define
Key Takeaways Explain This Topic AI
A backlog is a prioritized list of work; PRINCE2 Agile distinguishes the project backlog, owned at project level, from the delivery (product) backlog worked by a team.
A timebox is a fixed period of time that cannot be extended — iterations, releases and stages are all timeboxes at different scales.
A release map schedules when features will be delivered across the project, linking releases to the benefits they unlock.
The project canvas is a single-page artifact capturing the project's purpose, users, outcomes and constraints, produced collaboratively in a project canvas workshop.
An epic user story is a large user story that is too big to deliver in one iteration and will be broken down into smaller stories.
Last updated: August 2026
1.3 PRINCE2 Agile Key Terms You Must Be Able to Define
Quick summary: The syllabus names eight glossary terms you must be able to define at Bloom's level 1: backlog (project and product), benefit , dashboard (project and team), epic user story , project canvas , release map , timebox (iteration, release, stage) and waterfall . These recur as missing-word and standard questions, and several of them are Version 2 additions that do not appear in older PRINCE2 Agile material at all.
Backlog — project and product
A backlog is a prioritized list of everything that might be delivered. It is not a specification and not a contract: it is a living, ordered queue that is refined continuously.
PRINCE2 Agile distinguishes two scales:
The project backlog holds requirements at project level. It is the project's view of what could be built, expressed at a level the project board and the chief product owner can reason about. Requirements are expressed here.
The delivery (product) backlog is what an individual delivery team works from. Items are smaller, closer to ready, and refined into user stories the team can size and pull into an iteration.
The relationship between them is one of the chief product owner's central responsibilities: keeping the project backlog and the delivery teams' product backlogs aligned so that teams are building the things the project actually needs next.
Benefit
A benefit is a measurable improvement resulting from an outcome that is perceived as an advantage by one or more stakeholders. Three parts of that definition earn marks:
Measurable — if you cannot measure it, you cannot demonstrate it was realized.
Resulting from an outcome — the project delivers outputs (products); outputs enable outcomes (changes in behaviour or capability); outcomes yield benefits. A new system is an output, not a benefit.
Perceived as an advantage by stakeholders — the same outcome may be a benefit to one group and a dis-benefit to another.
Benefits drive the business case practice, and in an agile context they are the reason frequent releases matter: an early release can start realizing benefits long before the project closes.
Dashboard — project and team
A dashboard is a visual, at-a-glance display of current status, designed to be read rather than studied.
A project dashboard shows the project manager and project board where the project stands: progress against the release map, tolerance consumption, top risks and issues, benefit forecasts.
A team dashboard shows a delivery team its own state: work in progress, blockers, burn charts, Definition of Done compliance.
Dashboards are the agile answer to the question "how do we keep the board informed without writing reports nobody reads?" Maintaining the information held on project dashboards is a named responsibility, and a team dashboard is one of the things a kickoff workshop establishes.
Epic user story
A user story expresses a requirement from the user's point of view, conventionally in the form "As a [role], I want [capability], so that [benefit]."
An epic user story is simply a user story that is too large to be delivered within a single iteration . It is a placeholder for a body of work that will be decomposed into smaller stories as it approaches the top of the backlog. Epics let a team hold long-range scope in the backlog without pretending to know detail it does not yet have.
Project canvas
The project canvas is a single-page artifact that captures the essence of the project: its purpose, the user groups it serves, the outcomes and benefits sought, the constraints, and the high-level approach. It is deliberately one page so that it can be read, challenged and revised in a room full of people.
It is produced collaboratively in a project canvas workshop , in which the user groups are defined and prioritized. Because it is short and visual, it is far more likely to be kept current than a long project brief — and it is one of the artifacts most amenable to being drafted quickly with AI assistance and then verified by a human.
Release map
A release map shows when features will be delivered across the life of the project. It sits between the project backlog and the plans practice: it takes prioritized requirements and schedules them into releases, so that everyone can see which capability lands when, and therefore when each benefit starts to accrue.
The release map is updated as part of the planning approach — specifically when the plan is documented — and it is a standing input to release planning workshops and stage boundary decisions.
Timebox — iteration, release, stage
A timebox is a fixed period of time that cannot be extended . When work will not fit, the scope of the timebox flexes; the end date does not move. PRINCE2 Agile uses timeboxes at three nested scales:
- Timebox Typical length Owned by Contains
- Iteration 1–4 weeks Delivery team Stories drawn from the delivery backlog
- Release Weeks to a few months Project manager with the product owner One or more iterations
- Stage A management control period Project board via the project manager One or more releases
The nesting matters: a stage is not a sprint . Stages exist for management control and end at a stage boundary where the board decides whether to continue. Iterations exist for delivery cadence. Conflating them is a classic exam trap.
Waterfall
Waterfall is a sequential, linear delivery approach in which each phase — requirements, design, build, test, deploy — is completed before the next begins. Everything is specified up front, and change is handled by formal change control.
PRINCE2 Agile does not treat waterfall as an error. It treats it as an approach that suits stable, well-understood, heavily regulated work, and treats iterative and incremental delivery as suiting work where requirements will be discovered. A project may legitimately use both: waterfall for a hardware sub-project, iterative delivery for the software around it.
- Term One-line definition
- Backlog Prioritized list of work; project-level or team-level
- Benefit Measurable improvement from an outcome, seen as an advantage by stakeholders
- Dashboard Visual at-a-glance status display, at project or team level
- Epic user story A user story too large for one iteration, to be broken down
- Project canvas Single-page artifact capturing purpose, users, outcomes and constraints
- Release map Schedule of when features will be delivered
- Timebox Fixed, non-extendable period; iteration, release or stage
- Waterfall Sequential delivery approach with phases completed in turn