What is burndown?
A burndown is a simple visual chart that shows how much work remains in a project over time. It starts with the total amount of tasks (or story points) at the beginning of a sprint and drops down as work gets completed, ideally reaching zero by the deadline.
Let's break it down
- Axis: The horizontal line (X‑axis) represents time, usually days of a sprint. The vertical line (Y‑axis) represents the amount of work left.
- Line: The line on the chart slopes downward as tasks are finished. Each point on the line tells you “how much work is still open” on that day.
- Ideal line: A straight diagonal line from the start point to zero at the end shows the perfect pace. Your actual line is compared to this to see if you’re on track.
Why does it matter?
It gives the whole team a quick, at‑a‑glance view of progress. If the line is above the ideal line, you’re falling behind; if it’s below, you’re ahead. This helps spot problems early, adjust plans, and keep stakeholders informed.
Where is it used?
Burndown charts are a staple in Agile and Scrum environments. Teams use them in software development, product design, marketing campaigns, and any project that works in short, time‑boxed iterations (sprints).
Good things about it
- Simple: Easy to read for both technical and non‑technical people.
- Immediate feedback: Shows progress daily, so issues are caught early.
- Motivating: Watching the line drop can boost team morale.
- Data‑driven: Helps improve future sprint estimates by showing real velocity.
Not-so-good things
- Only measures quantity, not quality: It doesn’t show if the work done is actually good or meets requirements.
- Can be misleading: If tasks are re‑estimated or added mid‑sprint, the chart may look worse even though the team is working hard.
- Over‑focus on the chart: Teams might rush to close tasks just to make the line look better, sacrificing thoroughness.
- Requires accurate tracking: If work isn’t logged correctly, the chart becomes unreliable.