# Burndown Chart

A burndown chart plots work remaining over time, often against a reference line that reaches zero at the end of a sprint or delivery horizon.

- Type: artifact
- Domain: Delivery & agility
- Level: Foundational
- Last reviewed: 2026-09-22
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/burndown-chart/>)

## What it means

A burndown chart shows how much work remains as time passes. Time appears on the horizontal axis and remaining items, points, hours, or another agreed unit on the vertical axis. Many charts add an ideal or planned line from starting scope to zero, providing a reference rather than a law of how work must finish.

## Why it matters

Burndown offers a compact signal about whether a time-boxed body of work is progressing. Plateaus can prompt discussion of blockers, delayed acceptance, or work that is too large; sudden drops can reveal batching or late updates. Its value is the conversation it triggers, not visual conformity to the ideal line.

## When to use it

Use burndown for a sprint or another short horizon with a clear end and relatively stable scope. It works best when remaining work is updated consistently and the team can respond to emerging risk. Prefer burnup when scope change needs to be shown explicitly rather than inferred from jumps.

## How it works

1. Set the time box, included work, done rule, and vertical-axis unit before tracking begins.
2. Record remaining work at a consistent daily or periodic cutoff.
3. Plot actual remaining work and, if useful, a clearly labeled reference trajectory to zero.
4. Investigate plateaus, increases, and late drops through item-level evidence and team discussion.
5. At the review or retrospective, connect patterns to planning, slicing, flow, quality, and scope decisions.

## A practical example

A two-week sprint begins with 52 points. The line stays flat for four days although several items are nearly complete. The team discovers that stories are too large and acceptance happens only on Fridays. It slices upcoming work more narrowly and reviews continuously, using the next burndown as feedback rather than demanding a straight line.

## Where it breaks

Burndown can hide whether remaining work changed because scope, estimates, or completion changed. An ideal line may imply false precision, and point-based charts inherit estimation inconsistencies. The chart says little about value, quality, individual contribution, or unfinished-item age. Smoothness can be gamed through updates or selective completion.

## Common mistakes

- Treating deviation from the ideal line as failure instead of a prompt to inspect current risk.
- Ignoring scope additions or removals that alter remaining work during the period.
- Using the chart to pressure individuals or to reward a cosmetically smooth descent.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/burndown-chart/#visualization-burndown-chart>)

## Sources

1. [Agile Burndown Chart Tutorial](<https://www.atlassian.com/agile/tutorials/burndown-charts>) — Atlassian · Professional guide
2. [Configure Burndown and Burnup Widgets](<https://learn.microsoft.com/en-us/azure/devops/report/dashboards/configure-burndown-burnup-widgets?view=azure-devops>) — Microsoft Learn · Technical documentation

## Related topics

- [Burnup Chart](<https://wiki.soroush.uk/topic/burnup-chart/>)
- [Team Velocity](<https://wiki.soroush.uk/topic/team-velocity/>)
- [Cumulative Flow Diagram](<https://wiki.soroush.uk/topic/cumulative-flow-diagram/>)
