Velocity and Burndown Charts for the PMP Exam: A Complete Guide

Why Agile Metrics Matter on the PMP Exam

The PMP exam tests your ability to use data for decision-making, and in agile contexts, velocity and burndown charts are two of the most important tools. You need to know what they measure, how to interpret them, and what actions to take based on what they reveal.

Understanding Velocity

Velocity is the amount of work a team completes during a sprint, measured in the same units used for estimation (typically story points). If a team completes user stories totaling 34 story points in Sprint 5, their velocity for that sprint is 34.

How Velocity Is Used

Sprint planning — The team uses average velocity from recent sprints to forecast how much work they can take on. If the team's average velocity over the last 3 sprints is 30 story points, they should plan for roughly 30 points.
Release planning — If 200 story points remain in the backlog and the team's average velocity is 30, you can estimate roughly 7 sprints (about 14 weeks for two-week sprints) to complete the work.
Trend analysis — Tracking velocity over time reveals patterns. Consistently declining velocity may indicate impediments, technical debt, or team burnout.

What Velocity Is NOT

This is critical for the PMP exam:

Velocity is not a performance metric. It should never be used to compare teams or to pressure a team to increase output.
Velocity is not constant. It fluctuates naturally sprint to sprint. Use a rolling average (typically 3-5 sprints) for planning.
Velocity is not transferable. One team's velocity means nothing for another team because estimation approaches differ.

Understanding Burndown Charts

A burndown chart is a graphical representation of work remaining versus time. It shows whether the team is on track to complete the planned work by the end of the sprint (or release).

Sprint Burndown

The sprint burndown chart plots remaining work (in story points or hours) on the Y-axis against sprint days on the X-axis. An ideal burndown shows a steady diagonal line from the total planned work down to zero. In reality, the line is usually jagged — work gets completed in bursts, sometimes new work is discovered, and some days have more progress than others.

Reading a Burndown Chart

When interpreting a burndown chart for the PMP exam, look for these patterns:

Line above the ideal — The team is behind schedule. Work is being completed slower than planned.
Line below the ideal — The team is ahead of schedule. They may be able to pull in additional work.
Flat line — No work is being completed. Something is blocking the team.
Line goes up — Work was added mid-sprint (scope creep) or the team discovered previously unaccounted work.

Release Burndown

A release burndown tracks total remaining work across multiple sprints. It's used for longer-term forecasting and stakeholder communication. Unlike sprint burndowns, release burndowns update once per sprint rather than daily.

Burndown vs. Burnup Charts

A burnup chart shows work completed over time rather than work remaining. The advantage of a burnup chart is that it makes scope changes visible — if the total scope line moves up, stakeholders can see that new work was added. Burndown charts can obscure this because added scope and completed work can cancel each other out visually.

Exam Application

When you encounter a question showing a burndown chart, read it carefully. Ask yourself: Is the team on track? If not, what's the likely cause? What should the project manager do? The answer usually involves a conversation — at the Daily Scrum, in a retrospective, or with the Product Owner about scope.

Practice interpreting charts and other agile metrics with PMPprep's visual question sets. Check out our cheat sheets for a printable quick-reference on agile metrics.