Burndown chart

What is a burndown chart?

Although not included formally in the scrum framework, a burndown chart is an optional tool that visually tracks the remaining work in a sprint or project over time. The horizontal axis shows time, and the vertical axis shows the amount of work remaining, typically measured in story points, task hours, or backlog items. 

As the team completes work, the plotted line trends downward, providing a simple way to see progress at a glance. If the scope changes mid-sprint, it can be represented on the chart with a vertical line, showing that the total scope has shifted.

Agile teams may use burndown charts to monitor their work and identify trends in their progress. A sprint burndown chart focuses on work remaining within a single sprint, while a product burndown chart tracks progress toward completing an entire product backlog or release.

Why are burndown charts useful?

Burndown charts can help teams and stakeholders visualize progress in a simple way. When teams update the chart often, they'll notice patterns that help uncover obstacles or inefficiencies. If work is not decreasing as expected, they can identify issues early and adjust their approach.

Benefits of using a burndown chart

• You can see how much work is left and track whether or not you're on pace, which makes it easier to stay on track during the sprint.
• Frequent updates help you notice when you're off track so you can course-correct sooner.
• Having the chart visible keeps progress top-of-mind and encourages team discussions around improving collaboration.

Common challenges with burndown charts

While burndown charts provide helpful snapshots of progress, they have limitations. For instance, while they can reflect changes in scope (often shown as vertical lines to indicate added or removed work), not every team uses them this way or updates them consistently. When charts aren't annotated, scope changes can make progress appear off-track, even if the team is responding to new information or shifting priorities. And while a burndown chart shows how much work is complete, it doesn't show which backlog items are done. A team might be hitting the ideal burn line but not necessarily delivering the most valuable work. That's why burndown charts work best alongside regular discussion and other tools that keep the team aligned on value.

Frequently asked questions

How is a burndown chart different from a burnup chart?

A burndown chart tracks only the remaining work, while a burnup chart shows completed work and projected backlog size. Burnup charts provide better visibility into changes in scope, helping teams understand whether progress is due to work completion or backlog adjustments.

Why doesn't our burndown chart always show a steady decline?

Burndown charts don't always move in a straight line because work doesn't always go as planned. Tasks might take longer than expected, new work could be added, or progress updates might be missing. Checking in regularly helps teams spot any issues and adjust as needed.

Does every scrum team need to use a burndown chart?

Scrum doesn't require teams to use burndown charts, but some find them useful for tracking progress. Others prefer different tools, like burnup charts or cumulative flow diagrams, especially if they want to see changes in scope over time. The best tracking method depends on what gives the team and stakeholders the clearest view of progress.

How often should teams update a burndown chart?

Keeping the burndown chart updated daily gives the team the most realistic view of their progress. When the team tracks changes regularly, they can catch slowdowns early, diagnose what's causing them, and adjust their approach before small issues become big problems. If the chart isn't updated consistently, it might show an inaccurate picture of how much work is left and make it harder for the team to plan effectively.