What Is a Burndown Chart? How to Read and Use One in Agile
A burndown chart is a visual tool used in agile software development to track the amount of work remaining in a sprint or project over time. It plots two lines: the ideal progress line (showing how work should decrease if the team delivers at a steady pace) and the actual progress line (showing how work is actually decreasing based on what’s been completed). The goal is for the actual line to track below or along the ideal line — indicating the team is on pace to complete their committed work by the end of the sprint.
Burndown charts are most commonly used in Scrum — both at the sprint level (sprint burndown) and at the release or project level (release burndown). They provide real-time visibility into delivery progress that makes problems visible early, when there’s still time to respond.
How to Read a Burndown Chart
The Axes
- Vertical (Y) axis — Remaining work, usually measured in story points or hours
- Horizontal (X) axis — Time, measured in sprint days or calendar dates
The Lines
- Ideal burndown line — A straight diagonal from the total planned work at the sprint start to zero at the sprint end. Represents perfect, linear progress.
- Actual burndown line — Plots the remaining work at the end of each day based on what’s actually been completed.
What the Patterns Mean
Tracking along the ideal line: The team is making steady progress and is on pace to complete their commitment.
Actual line above the ideal line: The team is behind pace — more work remains than expected at this point. Intervention may be needed: descoping, resolving blockers, or adjusting expectations.
Actual line below the ideal line: The team is ahead of pace — they may complete the commitment early and could potentially pull in additional backlog items.
Flat actual line: No work is being completed — the team may be blocked, waiting on dependencies, or the burndown isn’t being updated.
Sudden drops: Large amounts of work completed in a single day. May reflect work done but not updated daily, or work that was removed from scope rather than completed.
Upward movement: Work added to the sprint. This is a scope management signal — additions during a sprint should be intentional and understood by the team.
Sprint Burndown vs. Release Burndown
Sprint burndown tracks work remaining within a single sprint. Updated daily. The primary operational tool for teams managing sprint-level delivery.
Release burndown tracks work remaining across a full release cycle — potentially spanning many sprints. Updated per sprint. Used to forecast whether a release will complete on schedule and to identify trends in team velocity over time.
Limitations of Burndown Charts
They don’t reveal quality: A burndown that reaches zero doesn’t mean the work was done well — only that tasks were marked complete.
They can be gamed: Teams that feel pressure to show progress may mark items complete before they’re fully done, or remove scope rather than reporting the true remaining work.
They don’t show individual performance: Burndown charts reflect team-level progress, not individual contributions.
They can create the wrong focus: Teams that optimize for the burndown line — getting to zero — rather than for delivering value may make poor scope decisions.
What to Do When the Burndown Shows Problems
If the team is consistently behind the ideal line:
- Review blockers in the daily scrum and address them aggressively
- Reassess the sprint backlog — is the remaining work accurately estimated? Is scope in line with capacity?
- Consider whether stories can be split into smaller, deliverable pieces
- Have a transparent conversation with the Product Owner about what can realistically be completed
If the team frequently finishes well under the ideal line:
- Check whether estimations are systematically too generous
- Consider whether stories are being broken down small enough
- Evaluate whether the velocity data can be used to take on more ambitious sprint goals
Key Takeaways
A burndown chart is a simple but informative tool for tracking sprint progress and identifying delivery risks early. Its value lies in making the status of sprint work visible to the whole team — not just the Scrum Master — and in creating a shared understanding of whether the team is on track to meet its commitment. Used alongside daily standups and sprint reviews, it provides the real-time feedback loop that keeps agile teams accountable and enables early course correction.