Study guide

4.1 Projects, Project Management and the Seven Performance Targets

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

4.1 Projects, Project Management and the Seven Performance Targets

Key Takeaways Explain This Topic AI

PRINCE2 defines a project as a temporary organization created to deliver one or more products according to an agreed business case.

Version 2 aligns with PRINCE2 7's seven performance targets: benefits, cost, time, quality, scope, sustainability and risk.

Sustainability is the seventh target added in PRINCE2 7 and carried into PRINCE2 Agile Version 2 — it covers environmental, social and economic impact.

A performance target is the baseline against which project success is measured, and each target carries a tolerance.

In agile delivery, time and cost are normally held firm while scope flexes, so that deadlines and budgets are protected.

Last updated: August 2026

4.1 Projects, Project Management and the Seven Performance Targets

Quick summary: A project is a temporary organization created to deliver one or more products according to an agreed business case . Project management is planning, delegating, monitoring and controlling all aspects of it. Version 2 measures success against seven performance targets adopted from PRINCE2 Project Management Version 7: benefits, cost, time, quality, scope, sustainability and risk .

Project and project management

A project is a temporary organization that is created for the purpose of delivering one or more business products according to an agreed business case. Unpacking that:

Temporary organization — a project is not just a piece of work, it is a structure of people with defined roles, created and then dissolved.

One or more business products — projects deliver outputs; those outputs enable outcomes; those outcomes realize benefits.

According to an agreed business case — the justification is not optional and not a one-off. It is agreed at the start and re-tested throughout.

Project management is the planning, delegating, monitoring and control of all aspects of the project, and the motivation of those involved, to achieve the project objectives within the expected performance targets.

The four characteristics that separate a project from business as usual, from section 2.1, are that it is temporary , unique , introduces change , and is delivered by a cross-functional team.

The seven performance targets

This is the single largest structural change from Version 1, and it is very likely to be examined.

Version 1 of PRINCE2 Agile taught the hexagon : six project performance aspects — time, cost, quality, scope, risk and benefits — with rules about which are fixed and which flex. Version 2 replaces the hexagon with the seven performance targets adopted from PRINCE2 7 , which add sustainability as a seventh.

A performance target is the baseline against which the success of the project is measured. Each carries a tolerance : the permitted deviation before the matter must be escalated under the manage-by-exception principle.

Performance target The question it answers Typical agile treatment

Benefits What measurable improvements will this deliver, and are they still expected? Re-forecast at every stage boundary; realized progressively through frequent releases

Cost What will it cost? Normally held firm — a stable team over a fixed number of timeboxes gives a predictable burn rate

  • Time When will it be delivered? Normally held firm — timeboxes do not extend
  • Quality How good must the product be? Protected by a non-negotiable Definition of Done and continuous testing
  • Scope What will and will not be delivered? The variable that flexes , managed by prioritization such as MoSCoW

Sustainability What is the environmental, social and economic impact? Assessed in the business case; sustainability targets and tolerances set alongside the others

Risk What uncertainty are we prepared to carry? Reduced structurally by short feedback loops; managed within an agreed risk appetite

Sustainability — the target candidates forget

Sustainability entered PRINCE2 with Version 7 and is carried into PRINCE2 Agile Version 2. It asks the project to account for environmental, social and economic impact rather than financial return alone — energy consumption, materials, accessibility, social outcomes, and the long-term maintainability of what is built.

Practically, it appears in the business case alongside the financial appraisal, it can carry its own targets and tolerances, and it connects to agile sustainability — the idea that a delivery pace and a way of working must be maintainable over the long run rather than burning teams out. If a question lists six of the targets and asks which is missing, sustainability is very often the answer.

Fixing and flexing in an agile context

The underlying logic that made Version 1's hexagon useful survives into Version 2's targets, even though the diagram is gone.

In a plan-driven project, scope is treated as fixed and everything specified must be delivered. When reality intervenes, the only variables left to absorb it are time (the project runs late) and cost (it overspends) — and, in practice, quality, because compressed testing is the first casualty of a deadline crunch.

In agile delivery this is inverted. Time and cost are held firm and scope flexes . When an iteration cannot fit everything, the lowest-priority items drop out and the timebox still ends on its date.

For this to be legitimate rather than a euphemism for under-delivery, three conditions must hold:

The backlog is genuinely prioritized , so that what drops out is the least valuable work, not the last work looked at.

Quality does not flex. The Definition of Done is the guard-rail; dropping scope is permitted, dropping testing is not.

The customer accepts that not everything is needed. The lowest-priority tail of a requirements list rarely repays its cost, and an honest prioritization exercise usually reveals a great deal of it.

MoSCoW prioritization is the standard tool: Must have (without which the release is worthless), Should have (important, painful to omit, but there is a workaround), Could have (desirable, dropped first under pressure), and Won't have this time (explicitly excluded from this timebox, so that it is decided rather than forgotten). The Won't have category is the one candidates forget — its value is that exclusion is made explicit rather than left ambiguous.

The flexible scope lives in the Should and Could categories. If everything in a release is a Must have, there is no flexibility, and the project has quietly returned to fixed scope with all the risk that entails.

Loading diagram... Which targets hold firm and which flex