Study guide

8.5 The Progress 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.5 The Progress Practice in an Agile Context

Key Takeaways Explain This Topic AI

The progress practice compares what has been delivered with what was planned, forecasts the outturn, and controls deviations causing an exception.

A purpose of the progress practice is to control any deviations causing an exception — the phrasing used in missing-word questions.

Progress in agile is measured by working product completed against the Definition of Done, not by percentage-complete estimates.

Tolerances are set for each performance target at each level, and a forecast breach triggers an exception report to the level above.

Time-driven controls such as highlight reports run on a cycle; event-driven controls such as exception reports are triggered by circumstances.

Last updated: August 2026

8.5 The Progress Practice in an Agile Context

Quick summary: The progress practice monitors and compares what has been delivered with what was planned , forecasts the outturn, and controls any deviations causing an exception . In an agile project, progress is measured by working product meeting the Definition of Done — the only measure that cannot be inflated.

Purpose

The purpose of the progress practice is to establish mechanisms to monitor and compare actual achievements against those planned, to provide a forecast of the project's objectives and continued viability, and to control any unacceptable deviations.

Two phrasings recur in exam questions and are worth memorising verbatim:

"By comparing what has been delivered with what was planned" — this identifies progress in a purpose question.

"A purpose of the [ ? ] practice is to control any deviations causing an exception" — the missing word is progress .

Why working product is the honest measure

The traditional measure is percentage complete, and it is unreliable for a well-known reason: it is self-reported against work that cannot be independently inspected. The "90% complete" that stays 90% complete for two months is a standing joke because the last increment of effort is where all the unknowns live.

Agile replaces it with a binary test at item level. An item either meets the Definition of Done or it does not; there is no partial credit. That makes progress:

Objective. The Definition of Done is written down and checkable.

Non-inflatable. You cannot claim eight-tenths of done.

Meaningful. Completed items are usable, so completion corresponds to value rather than to effort expended.

Aggregate that across an iteration and you get velocity ; plot it and you get a burn chart ; publish it and you get a dashboard .

What progress is measured with

  • Instrument What it shows Level
  • Burn-down chart Work remaining falling towards zero Iteration
  • Burn-up chart Work completed rising towards a scope line that may move Release, stage
  • Velocity Points completed per iteration; supports forecasting Team
  • Team dashboard Current state of the team's work, blockers, quality Delivery
  • Project dashboard Progress against the release map, tolerance consumption, risks, benefit forecast Project
  • Cumulative flow Work in progress and where it accumulates Flow-based delivery

The burn-up chart is preferred at release and stage level because it draws total scope as a separate line, so scope flexing is visible rather than concealed — which matters precisely because scope is the variable that flexes.

Tolerances and exceptions

Progress is the practice through which manage by exception operates.

Tolerances are set for each performance target — benefits, cost, time, quality, scope, sustainability, risk — at each level of the project. Within its tolerance, a level acts without referring upward.

The delegation cascade:

  • Level Sets tolerances for Escalates to
  • Corporate / programme / customer The project —
  • Project board The stage Corporate, programme or the customer
  • Project manager The work package Project board
  • Team Within the work package Project manager

When a level forecasts that it will breach its tolerance, it raises an exception to the level above. Note the word: the trigger is the forecast , not the actual breach. Waiting until the tolerance has already been exceeded removes the level above's ability to act.

A tolerance is not a target and not a buffer to be consumed. It is the limit of delegated authority.

Time-driven and event-driven controls

Control Type What it is

Checkpoint report Time-driven Team to project manager, on an agreed frequency — often replaced by a live team dashboard

  • Highlight report Time-driven Project manager to project board, on an agreed frequency
  • Progress review workshop Time-driven Collaborative review of where the project stands
  • End stage report Event-driven Produced at a stage boundary
  • Exception report Event-driven Produced when a tolerance is forecast to be breached
  • Issue report Event-driven Produced for a significant issue

The distinction is simply what triggers the control: a date for time-driven, a circumstance for event-driven.

Tailoring progress for agile

Reporting shifts from push to pull. A live dashboard the board can consult at any time is better than a weekly document, because it is current and it costs the team nothing to produce.

Reports become thinner, not absent. The highlight report still exists; it summarises tolerance consumption, forecast, exceptions and benefit position, drawing on data the team generates anyway.

Forecasting uses velocity rather than remaining-effort estimates.

Progress is reviewed at multiple cadences : continuously by the team, at each iteration review, at the progress review workshop, and formally at each stage boundary.

The governing intent is that reporting should be a by-product of delivery , not a separate activity performed for the benefit of management. When a team spends a day a fortnight producing a report nobody reads, the progress practice has been implemented badly.