Burndown Chart
DE: Burndown-Diagramm
A chart showing remaining work versus time in a sprint or project.
Detailed Explanation
A burndown chart tracks remaining work over time. The vertical axis shows work (story points or hours), the horizontal axis shows time (sprint days). An ideal line slopes from total work at sprint start to zero at sprint end.
When actual progress is above the ideal line, the team is behind; below means ahead. Burndown charts provide instant visibility into sprint progress and help identify bottlenecks early. They are among the simplest yet most powerful Agile metrics.
Sprint burndown charts track individual sprints, while release burndown charts track multi-sprint progress toward a release goal. Both help maintain realistic delivery expectations.
Key Points
- Shows remaining work vs. time at a glance
- Ideal line represents even, perfect progress
- Above ideal = behind; below = ahead
- Updated daily during standup
- Sprint burndown vs. release burndown variants
- Reveals trends early for timely corrective action
Practical Example
A team starts a 2-week sprint with 40 story points. By day 5 the burndown shows 30 points remaining (ideal: 20). The Scrum Master raises this at standup. The team discovers two stories blocked by an API dependency. They swarm on the blocker and recover by day 8.
Tips for Learning and Applying
Update the burndown daily — it loses value if stale
Use it as a conversation starter, not a punishment tool
Do not manipulate points — transparency matters most
Combine with a burnup chart for release-level tracking
Related Terms
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.