In 30 seconds
- Y-axis: work remaining. X-axis: days in the sprint.
- An ideal line shows a steady pace; the actual line shows reality.
- Flat stretches and late cliffs are the signals to watch.
Try it
IdealActual
How to read it
The chart starts with the total work planned for the sprint, in story points, tasks or items. Each day, the line drops as work is finished. A straight "ideal" line from start to zero shows a steady pace for comparison.
Common patterns
| Pattern | Usually means |
|---|---|
| Flat, then a cliff at the end | Work isn't finished until late; items too big |
| Line goes up | Scope added mid-sprint |
| Hits zero early | Under-committed, or estimates too high |
| Tracks the ideal line | Small items, steady flow |
Burndown vs burnup
A burndown shows only what's left, so added scope looks like no progress. A burnup chart plots completed work and total scope as two lines, making scope changes visible. Release tracking often uses burnup; sprints often use burndown.
Myth vs reality
Myth · A burndown measures productivity.
Reality · It shows progress toward a plan, not how hard people work.
Myth · Deviating from the ideal line is failure.
Reality · It's a signal to talk, not a score.
Myth · Scrum requires a burndown.
Reality · It's optional; any way of tracking progress works.
FAQ
What unit should we burn down?
Story points, task hours or item count. Item count is simplest if items are similar in size.
Should we update it daily?
Yes. Most tools update it automatically as items move.
Can it be used for releases?
Yes, with sprints on the x-axis instead of days.