Study guide

6.2 The Purpose of the Seven PRINCE2 Agile Practices

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

6.2 The Purpose of the Seven PRINCE2 Agile Practices

Key Takeaways Explain This Topic AI

The seven practices are business case, organization, plans, quality, risk, issues and progress — all seven addressed continually throughout the project.

Practices are the Version 7 term for what earlier editions called themes, and the old Change theme is now the Issues practice.

The business case practice judges whether the project is desirable, viable and achievable; the organization practice defines the project's responsibilities.

The plans practice estimates how much work is to be delivered and when; the progress practice compares what has been delivered with what was planned.

The issues practice controls changes to the project's baseline, and a purpose of the progress practice is to control deviations causing an exception.

Last updated: August 2026

6.2 The Purpose of the Seven PRINCE2 Agile Practices

Quick summary: Seven practices, each addressed continually throughout the project rather than completed once: business case, organization, plans, quality, risk, issues, progress . Their purpose statements are directly examinable — expect both standard questions ("which practice has the purpose of…") and missing-word questions ("a purpose of the [ ? ] practice is to…").

Practices, not themes

PRINCE2 Version 7 renamed themes to practices , and PRINCE2 Agile Version 2 follows. This is not merely cosmetic: practice carries the sense of something you do continually , which is precisely the point. You do not "complete" the risk practice in week three; you attend to risk from before the project starts until after it closes.

The list also changed. The old Change theme is now the Issues practice. If your notes list Business Case, Organization, Quality, Plans, Risk, Change , Progress, they describe the pre-Version-7 structure.

  • Old term (Version 1 / PRINCE2 6) Current term (Version 2 / PRINCE2 7)
  • Themes Practices
  • Change theme Issues practice
  • Management products Artifacts
  • The seven purposes

Practice Purpose The question it answers

Business case To support decision making by judging whether the project is, and remains, desirable, viable and achievable Is this worth doing, and is it still worth doing?

Organization To define the project's responsibilities and establish its structure of accountability Who is accountable for what, and how do the roles relate?

Plans To facilitate communication and control by estimating how much work is to be delivered and when , and by what means What will be delivered, by whom, by when, and at what cost?

Quality To ensure that the users' requirements and expectations for the project's products are met Will the product be fit for purpose, and how will we know?

Risk To identify, assess and control uncertainty — threats and opportunities — during the project What might happen, and what will we do about it?

Issues To address issues and control changes to the project's baseline Something has happened or been requested — what do we do?

Progress To monitor and compare what has been delivered with what was planned , forecast, and control any deviations causing an exception Where are we, where will we end up, and do we need to escalate?

Getting the distinctions right

Purpose questions are usually testing whether you can separate two practices that overlap in ordinary language.

Business case vs plans

The business case asks whether the project should happen: is it desirable, viable and achievable? Plans ask how much and when : estimating the work and scheduling it. If the option mentions desirable, viable and achievable , it is the business case. If it mentions estimating how much work is to be delivered and when , it is plans.

Progress vs plans

Plans set the baseline; progress compares reality to it. If the option mentions comparing what has been delivered with what was planned , it is progress. If it mentions estimating and scheduling, it is plans. Progress also owns controlling deviations that cause an exception — that phrasing is the giveaway in a missing-word question.

Issues vs risk

Risk is about uncertainty — something that has not happened. A risk is a possible future event, and it is either a threat or an opportunity. Issues concern things that have happened or been requested now — a problem, a concern, an off-specification, or a request for change. The moment a risk materialises, it becomes an issue.

The other half of the issues practice is change control : controlling changes to the project's baseline. That is the phrase that identifies it.

Quality vs organization

Quality concerns whether the product meets the users' requirements and expectations. Organization concerns who is accountable for what. If a question asks which practice has the purpose of defining the project's responsibilities , the answer is organization .

Practices in an agile context

Each practice is tailored rather than dropped. Chapters 7 and 8 cover them in detail; in outline:

Business case — right-sized, potentially held on the project canvas, re-tested against evidence from each release; benefits realized progressively.

Organization — PRINCE2 project roles integrated with agile delivery roles, with a chief product owner where multiple teams are involved.

Plans — planned in layers: a release map for the project, plans for stages, and the delivery team planning its own iterations. Estimation is relative.

Quality — expressed through acceptance criteria, the Definition of Ready, the Definition of Done and continuous testing rather than a single late test phase.

Risk — reduced structurally by short feedback loops; risks surfaced in iterations, stages, retrospectives and progress reviews.

Issues — change embraced at the delivery level by re-prioritizing the backlog inside a fixed timebox, with formal change control reserved for changes to the baseline itself.

Progress — tracked with burn charts, dashboards and working increments, rather than percentage-complete estimates.

The constant across all seven is that what is tailored is the form and formality, never the purpose . The business case may be a page rather than a document, but the project still has to be desirable, viable and achievable.

Loading diagram... The seven practices and the question each answers