Burndown Chart: A Project's Fuel Gauge
A burndown chart is a project's fuel gauge, showing work left versus time. Scrum teams use it to track sprint progress and predict completion. The footgun is treating it as a performance report instead of a conversation starter about blockers.
THE MENTAL MODEL: Think of a burndown chart as a project's fuel gauge. It provides a simple, visual answer to the question, "Are we on track to finish?" It plots the remaining work against time, with the goal of the line "burning down" to zero by the project's end date. The chart's value isn't in showing a perfect slope, but in making deviations from the ideal path immediately obvious.
HOW IT WORKS: A burndown chart has two axes. The vertical axis represents the total work remaining, often measured in story points, task counts, or hours. The horizontal axis represents time, such as the days in a sprint or weeks in a project. Each day, the team calculates the total work that is still outstanding and plots a new point. An "ideal" line is often drawn from the starting total on day one to zero on the final day. The team's actual progress is then plotted as a second line, allowing for a quick comparison against the ideal pace.
WHEN TO USE IT: Burndown charts are most effective for projects with a fixed scope and a fixed deadline, which is why they are a staple of Scrum sprints. They help teams self-manage and identify if they are falling behind, pulling ahead, or if the scope has unexpectedly increased. It is a tool for the team, by the team, to facilitate daily check-ins and adapt their plan.
WHEN NOT TO USE IT: The chart is less useful for projects without a clear endpoint or where the scope is expected to change constantly, such as in continuous flow models like Kanban. If work is not easily measurable or quantifiable (e.g., pure research or exploratory tasks), the chart can be misleading. Crucially, it should not be used by management to compare the performance of different teams, as each team's context and estimation scale is unique.
ONE CANONICAL EXAMPLE: A team starts a two-week (10-day) sprint with 50 story points of work. The ideal line on the chart runs from 50 points on Day 0 to 0 points on Day 10. On Day 2, they complete an 8-point story, so the actual work remaining is 42 points. On Day 4, they realize a task is more complex and re-estimate it, adding 3 points of work. The line on the chart goes up from 42 to 45. This isn't failure; it's a visual signal that new information has emerged, prompting a discussion about how to get back on track.
Read the original → en.wikipedia.org
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.