Study guide
8.1 The Quality 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
8.1 The Quality Practice in an Agile Context
Key Takeaways Explain This Topic AI
The quality practice ensures that the users' requirements and expectations for the project's products are met.
In the PRINCE2 Agile approach to quality, requirements are expressed in the project backlog rather than in a separate requirements specification.
Quality is protected rather than flexed: scope drops before quality does, because the Definition of Done is non-negotiable.
Quality is built in continuously through testing within each iteration, not inspected in during a late test phase.
Quality expectations and acceptance criteria come from the users; the senior user is accountable for specifying them.
Last updated: August 2026
8.1 The Quality Practice in an Agile Context
Quick summary: The quality practice exists to ensure that the users' requirements and expectations for the project's products are met. Its distinctive agile feature is that requirements are expressed in the project backlog , and that quality is built in continuously rather than inspected in at the end.
Purpose
The purpose of the quality practice is to ensure that the project's products meet the users' requirements and expectations, and are fit for purpose .
The phrase fit for purpose is doing real work. Quality in PRINCE2 is not "as good as possible" — it is "good enough for the use it will be put to, as agreed with the users". Gold-plating is a quality failure just as much as under-delivery is, because it consumes budget that the business case allocated elsewhere.
The PRINCE2 Agile approach: requirements in the project backlog
The characteristic statement of the quality practice in PRINCE2 Agile is that requirements are expressed in the project backlog .
This replaces the plan-driven pattern of a separate, signed-off requirements specification produced up front. Instead:
Requirements live in the project backlog as prioritized items, refined into user stories as they approach delivery.
Each item carries acceptance criteria — the specific, testable conditions for that item.
All items must additionally satisfy the Definition of Done , the standard that applies to everything.
The backlog is ordered by value , so the most important quality expectations are addressed first.
The benefit is that requirements stay current. A specification signed off in month one is a snapshot of what was understood in month one; a backlog is refined continuously as evidence arrives from real releases.
Be careful not to confuse this with the neighbouring practices. Benefits management actions and reviews should be defined belongs to the business case practice. Informal issues and required actions should be recorded belongs to the issues practice. Agile adoption issues are identified using the Agilometer belongs to the risk practice.
Quality is protected, not flexed
Of the seven performance targets, quality is one of those held firm in agile delivery, alongside time and cost. Scope is the variable that flexes.
The logic is straightforward. If a timebox is under pressure and quality is allowed to give, the team ships something that looks finished and returns weeks later as defects — which costs more than the scope that was protected. Worse, the degradation is invisible at the moment it happens, so governance cannot see it.
The mechanism that makes protection real is the Definition of Done . Because it is published, applies to every item, and is not variable by iteration, "we will drop a story" becomes the available response and "we will skip the regression tests" does not.
A nuance worth holding: PRINCE2 distinguishes quality criteria , which are fixed, from the quality tolerance attached to them. A criterion may legitimately carry a range — a page must load in under two seconds, with a tolerance to three — and that tolerance is agreed in advance rather than improvised under deadline pressure.
Who sets quality expectations
Quality expectations come from the users , not from the delivery team's professional judgement alone.
- Responsibility Role
- Specifies the users' quality expectations and acceptance criteria Senior user
- Represents those expectations in backlog ordering and refinement Product owner
- Ensures quality management is properly applied Project assurance
- Builds quality in and enforces the Definition of Done Delivery team, including testers
- Ensures the quality approach is agreed and applied across the project Project manager
Note that testers are a named delivery role in the Version 2 syllabus. Testing is part of the team's work within the iteration, not a downstream department the work is handed to.
Building quality in
The practical differences from a plan-driven approach:
Testing happens within the iteration , alongside development, so defects are found within hours rather than months.
Automated regression testing makes the Definition of Done affordable to enforce every iteration.
The product owner accepts or rejects each item against its acceptance criteria at the point it is completed.
Reviews inspect working product , so users see the real thing early and quality expectations are corrected while correction is cheap.
Technical debt is tracked , because the eventual consequence of poor design or poor development is debt that slows all future delivery.
Tailoring the quality practice
Regulated environments constrain how far quality documentation can be right-sized. Evidence that must be retained must still be produced — but it can be generated by the pipeline rather than written by hand.
The quality management approach is still agreed at initiation; what changes is that much of it is discharged through the Definition of Done and automated checks rather than through scheduled quality reviews.
The Definition of Done is agreed with, and visible to, the project board , because it is the guarantee underlying the fixed-quality target.