Skip to content
PMPCAPM

Burndown Chart

A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.

Share:

Know it well enough for the exam? Questions on Burndown Chart are scenario-based, not definitional.

Practice it free

Explanation

A sprint burndown is updated daily during each iteration, typically before or at the daily scrum, so the conversation starts from current data. A release burndown is updated once per sprint and tracks progress toward a release. Both are information radiators: displayed where everyone can see them, so the team and stakeholders get status without a report.

The chart has limits worth knowing. It combines progress and scope change into one line, so work added mid-release can hide work completed. A points-based burndown moves only when stories are done, while an hours-based one moves as effort is logged, which looks smoother but measures effort rather than completion. It is a tool for the team's self-management, not a measure of individual performance.

For a project manager acting as a servant leader, the burndown is a prompt for questions: why has the line been flat for three days, what is blocking the work, does the sprint backlog need renegotiating with the product owner? It is not a reason to demand overtime or to extend the sprint.

What a burndown chart tells you

A burndown chart answers one question at a glance: at this rate, will the remaining work be finished by the end of the timebox? The vertical axis is work remaining (story points, or task hours for some teams). The horizontal axis is time. A straight “ideal” line runs from the total at the start to zero at the end; the actual line is updated as work is completed. The gap between them is the story.

A sprint burndown covers one iteration, day by day. A release burndown covers several sprints, sprint by sprint, toward a release. Both are information radiators: big, visible, and owned by the team, so problems surface without anyone having to ask for a status report.

Worked example: a 10-day sprint

A team commits to 40 story points for a two-week sprint (10 working days). Points count only when a story meets the definition of done; there is no partial credit for a story that is 80% finished.

010203040012345678910Sprint dayStory points remainingflat: blocked
IdealActual remaining
Sprint burndown for the example. The ideal line falls 4 points per day; the actual line stalls on days 3–5 and finishes with 5 points not done.
DayIdealActualGapWhat happened
040400Sprint planning; 40 points committed
13640+4Stories started, none done yet (normal on day 1)
23236+4One 4-point story done
32833+5A 3-point story done; test environment goes down that evening
42433+9Nothing finishes; raised at the daily scrum
52033+13Environment restored late in the day
61628+12Two stories finish together
71223+11Team swarms on the largest open story
8818+10
9411+7Product owner and team agree one story will not make it
1005+5Sprint ends; one 5-point story goes back to the product backlog

Reading it

  • Days 3–5, flat line: no story reached done. The chart doesn't say why; the daily scrum does. Here it was an impediment (the test environment), which the team escalated.
  • Above the ideal line all sprint: the team is behind. By day 5 the gap is 13 points, a third of the commitment, which is a strong early warning.
  • Steeper than ideal from day 6: the recovery rate (about 5 to 7 points a day) is faster than the ideal pace, but not fast enough to close the gap.
  • Ending at 5, not 0: the sprint is not extended. The unfinished story goes back to the product backlog, gets re-ordered by the product owner, and the shortfall is a topic for the retrospective.

Points or hours?

Many teams burn down story points; others burn down the estimated hours of sprint tasks, which moves every day even when no story is done. Points-based charts look more like a staircase and are more honest about completion; hours-based charts show effort, which isn't the same as progress.

Common shapes and what they usually mean

ShapeLikely causeTypical response
Flat for several daysImpediment, or stories too large to finish quicklySurface at daily scrum; split stories; remove the blocker
Line goes upWork added mid-sprint, or remaining work re-estimated upwardCheck against the sprint goal; consider a burn-up to show scope separately
Cliff at the endWork is started early but finished late; big batch of testing at the endSmaller stories, limit work in progress, test continuously
Always below ideal, hits zero earlyUnder-commitment or padded estimatesUse actual velocity in the next sprint planning
Tracks the ideal line too perfectlyPossibly hours being burned to match the plan rather than measuredAsk what the chart is used for; avoid using it to judge individuals

Common exam traps

  • The Scrum Master or project manager updates the sprint burndown.

    The developers who do the work keep it current; it is their tool for self-management. The servant leader’s job is to remove the impediments the chart reveals.

  • The team is behind, so the answer is overtime or extending the sprint.

    PMI answers favour transparency and collaboration: discuss at the daily scrum, remove impediments, and if needed have the product owner and team renegotiate scope while keeping the sprint goal. Sprints are not extended, and sustainable pace matters.

  • Reading a flat line as "the team did nothing".

    A flat line means nothing reached done. Work may be in progress. That is why the chart prompts a conversation rather than a judgment.

  • Using a burndown when scope keeps changing.

    A burndown mixes progress and scope change into one line, so added work hides completed work. If the scenario stresses changing scope, the burn-up chart is the better answer.

  • Treating the burndown as mandatory Scrum.

    The Scrum Guide mentions burn-downs only as one optional way to forecast progress, alongside burn-ups and cumulative flow. It is a common practice, not a required artifact.

Burndown vs burn-up chart

BurndownBurn-up
PlotsWork remainingWork completed, plus a separate total-scope line
DirectionDown toward zeroUp toward the scope line
Scope changeHidden inside the remaining lineVisible as the scope line moving
Typical useSprint tracking, stable scopeRelease tracking, changing scope
Done whenLine reaches zeroCompleted line meets scope line

The burn-up chart page has a release example showing the same project both ways. For a longer comparison with real-world pitfalls, see Burndown chart vs burn-up chart on the blog.

Practice and related pages

Key Points

  • •Y-axis: work remaining; X-axis: time; the ideal line runs from the total to zero
  • •Above the ideal line = behind; below = ahead; flat = nothing reached done
  • •Sprint burndown is updated daily; release burndown is updated per sprint
  • •Owned and updated by the team; an information radiator, not a performance report
  • •It hides scope change, so use a burn-up chart when scope is moving

Exam Tip

A rising burndown line means work was added or re-estimated. A flat line means nothing met the definition of done, so investigate impediments rather than assume the team was idle. If the question is about showing scope change, choose the burn-up chart.

Frequently Asked Questions

Related Topics

High-yield topics our learners drill most before exam day.

Burn-Up Chart

A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.

Weighted Shortest Job First (WSJF)

Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.

Relative Estimation

Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.

Sprint Review

The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.

Sprint Backlog

The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.

Timeboxing

Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.

Resource Leveling

Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.

Deliverables

A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.

Power Interest Grid (Power/Influence Grid)

The power interest grid is a 2x2 stakeholder mapping tool that plots each stakeholder by power (ability to affect the project) and interest (concern about its outcome) to decide how to engage them: manage closely, keep satisfied, keep informed, or monitor.

Part of

Agile & Hybrid

Study full domain →

Practice Burndown Chart

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.