Burndown Chart: How to Read and Act on It
The burndown chart is one of the simplest and most powerful visual artifacts in Scrum. Yet teams often just look at it without taking action. Here’s how to extract action from every pattern the chart reveals.
What Is a Burndown Chart
A graph with two axes:
- X-axis: days of the sprint
- Y-axis: remaining story points
Two lines:
- Ideal: a straight diagonal from the total down to zero on the last day
- Actual: the real remaining points each day
Scenario 1: Clean Diagonal
The actual line closely follows the ideal line.
What it means: The sprint is on track.
Action: Keep going. In the daily, confirm there are no hidden risks lurking behind that pretty line.
Scenario 2: Plateau in the First Few Days
The line stays flat for the first 2-3 days before it starts dropping.
What it means: There may be initial complexity (setup, investigation) or blockers early in the sprint.
Action: Ask in the daily: “What’s preventing progress?” If it’s upfront complexity, that’s normal. If it’s a blocker, act on it.
Scenario 3: Sharp Drop at the End
The line stays mostly flat throughout the sprint and plummets in the last 2 days.
What it means: Cascade effect — everything gets delivered at once at the end. This means tasks aren’t being done in parallel or the Definition of Done is only being checked at the end.
Action: Encourage parallelism. Break larger items down. Move DoD verification into daily work, not just the last day.
Scenario 4: Line Going Up
Remaining points are increasing during the sprint.
What it means: Scope is being added mid-sprint.
Action: The Scrum Master should protect the sprint. New items belong in the backlog for the next sprint, not the current one. If something is truly urgent, remove something of similar size to keep things balanced.
Scenario 5: Never Hits Zero
The sprint ends and points are still left over.
What it means: The team overestimated its capacity, or blocked tasks went unresolved.
Action: In the retrospective, figure out whether it was overoptimistic estimating or unaddressed impediments. Adjust the next sprint’s planning accordingly.
Burndown vs. Burnup
Burndown shows the work remaining. It’s great for individual sprints.
Burnup shows the work completed, with a separate line for total scope. It’s better for releases and long-term projects because it makes scope growth visible.
Tools
- Jira: generates burndown charts automatically
- Azure DevOps: has native burndown and burnup charts
- Spreadsheets: perfectly functional for small teams
- Dev in Poker: records estimates that can feed external charting tools
Conclusion
A burndown chart is a thermometer, not a diagnosis. It tells you something is wrong — but it’s up to the team to investigate why and take action. Review it every day, and act when the pattern signals trouble.