Skip to content
Try Scrumling for Employers
Glossary · metrics

Burndown chart

A chart showing remaining work over time, commonly used to visualize progress within a Sprint, though not required by the Scrum Guide.

What it means

A burndown chart plots remaining effort or items on the vertical axis against time on the horizontal axis, typically trending toward zero as the Sprint progresses. It is a common practice, not a mandated Scrum artifact.

Teams use it to spot trends early: a flat line signals stalled progress, while a line steeper than the ideal trend can suggest scope was overestimated or work is going faster than expected.

Common mistakes

Burndown charts are less useful when scope changes frequently within a Sprint, since added or removed work distorts the line; some teams prefer a burnup chart, which separately tracks completed work against total scope.

Example

The team's Sprint burndown chart flattens on day six, prompting a mid-Sprint conversation about a blocked dependency.

How to read a burndown chart

The vertical axis shows the work still remaining, counted in items, tasks or estimate points. The horizontal axis shows the days of the Sprint. Each day the team records what is left, so the line moves down only when work is finished and up when work is added.

Many teams draw a straight guide line from the starting total to zero on the last day. That line is a reference, not a target. A real line that sits above it means more work remains than an even pace would suggest. A line below it means the team is ahead of an even pace. Steps, flat stretches and small rises are normal and are worth a conversation, not alarm.

Example: when scope changes mid-Sprint

A team starts a ten-day Sprint with 40 points of work. By day five the line shows 20 points remaining, right on the guide line. On day six the Product Owner and Developers agree to add an 8 point item that supports the Sprint Goal. On day seven the chart shows 26 points remaining even though the team finished 2 points that day.

Read without context, the rise looks like the team went backwards. In fact progress continued and the total grew. A note on the chart, or a burnup chart beside it, makes the scope change visible so nobody mistakes added work for lost work.

A falling line does not prove work is Done

The line only moves when someone marks work as complete. If items are moved to finished while testing, review or integration is still outstanding, the line can reach zero while the Increment does not meet the Definition of Done.

The chart reports what the team recorded, not the quality of what was built. The real check is whether each item meets the Definition of Done and whether the Increment can be inspected at the Sprint Review. Count an item as burned down only when it is truly Done.