Study guide

8.6 Progress Artifacts and Techniques: Burn Charts and Dashboards

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.6 Progress Artifacts and Techniques: Burn Charts and Dashboards

Key Takeaways Explain This Topic AI

Dashboards are the principal agile progress artifact, existing at both team and project level.

Information radiators make status visible continuously, so it has to be noticed rather than requested.

Burn-down charts suit a single fixed-scope iteration; burn-up charts suit releases and stages where scope flexes.

The progress review workshop is the collaborative forum in which progress is inspected and next steps agreed.

Highlight, checkpoint, end stage and exception reports remain, but are thinner and drawn from data the team already produces.

Last updated: August 2026

8.6 Progress Artifacts and Techniques: Burn Charts and Dashboards

Quick summary: Dashboards — team and project — are the primary agile progress artifact. Burn charts visualize the trend; burn-up charts are preferred where scope flexes. The progress review workshop is where progress is inspected collaboratively. PRINCE2's reports survive, thinner and drawn from data the team already generates.

Dashboards

A dashboard is a visual, at-a-glance display of current status designed to be read rather than studied. PRINCE2 Agile uses two.

The team dashboard

Shows the delivery team its own state, and is established in the kickoff workshop :

  • Work in progress and where it is queuing
  • Blockers and impediments
  • Burn-down for the current iteration
  • Definition of Done compliance and defect counts
  • Team agreements, values and norms

Its audience is the team itself. Its purpose is to let the team self-manage — a team that can see its own bottleneck fixes it without being told to.

The project dashboard

Shows the project manager and the project board where the project stands:

  • Progress against the release map
  • Tolerance consumption for each performance target
  • Top risks and open issues
  • Benefit forecast against the business case
  • Quality position and technical debt trend

Maintaining the information held on project dashboards is a named project responsibility — this is not something that maintains itself, and a stale dashboard is worse than none, because it is trusted while being wrong.

Information radiators

An information radiator is any highly visible display of information that broadcasts status continuously to anyone who passes it — a physical board, a wall-mounted screen, a shared page.

The principle behind them is that status should have to be noticed, not requested . In a traditional project, a stakeholder wanting to know how things are going asks the project manager, who assembles an answer — a cycle costing days and producing an answer already out of date. A radiator inverts this: the information is always there, always current, and available to everyone at the same time.

This connects directly to transparency as a characteristic of the agile mindset, and it depends on psychological safety : a team that fears the consequences of visible bad news will find ways to make the radiator show green.

Burn charts

Covered in section 3.2 and repeated here because they belong to this practice.

  • Burn-down Burn-up
  • Plots Work remaining Work completed, plus a total scope line
  • Direction Falls towards zero Rises towards the scope line
  • Scope change Hidden Visible
  • Best at Iteration level, fixed scope Release and stage level, flexing scope

The reason burn-up charts matter more in a PRINCE2 Agile project bears repeating: scope is the performance target that flexes, so governance needs to see the flexing. A burn-down chart absorbs added and dropped scope into a single line, leaving the board unable to tell a slow team from a growing scope.

Cumulative flow diagrams serve the same purpose in flow-based delivery, showing how much work sits in each state over time and therefore where work accumulates.

The progress review workshop

The progress review workshop is the collaborative forum in which progress is inspected and next steps agreed. It brings together the people who hold the information — the project manager, the product owner, the team, and the relevant board members — to look at the same evidence at the same time.

Its advantage over circulating a report is that questions can be answered in the room . A board member who does not understand why velocity has dropped can ask, and the answer can be given by the person who knows. It is also where the release map is re-tested against actual delivery, and where trade-offs — flexing scope, re-sequencing releases, escalating an exception — are agreed with everyone present.

The reports that survive

Agile does not abolish PRINCE2's reporting; it changes how the content is produced.

  • Report From → to Trigger Agile treatment
  • Checkpoint report Team → project manager Time-driven Often replaced entirely by a live team dashboard

Highlight report Project manager → project board Time-driven Thinner; assembled from dashboard data rather than written afresh

End stage report Project manager → project board Event-driven (stage boundary) Reports delivered increments and re-tested business case

Exception report Project manager → project board Event-driven (forecast breach) Unchanged in importance

End project report Project manager → project board Event-driven (closure) Includes what was actually delivered against the release map

The design intent throughout: reporting should be a by-product of delivering, not a parallel activity. If producing the highlight report requires the team to stop working and gather information that does not otherwise exist, the dashboards are not doing their job.

Velocity across six iterations, showing a new team stabilising