What does a burn-down chart show?

Remaining work on the vertical axis against time on the horizontal axis. The ideal line shows linear progress to zero; the actual line shows how the team really delivered.

Burn-down or burn-up — which is better?

Burn-down is clearer for fixed-scope sprints. Burn-up is more honest for releases where scope changes, because it separates completed work from total scope and exposes scope creep.

How often should I update the chart?

Daily, ideally during the stand-up. A weekly update turns the chart into a report; daily updates make it a conversation.

Why is my burn-down flat?

Almost always because work-in-progress is high but nothing is finishing. Swarm on the oldest item, finish it, then move to the next. Flat segments longer than two days warrant intervention.

Should the burn-down be in hours or story points?

Pick one and stay consistent. Hours work well for sprint-level forecasts; story points are better for cross-sprint velocity comparisons. Mixing the two makes the chart unreadable.

Can I use a burn-down in waterfall projects?

Yes — remaining items, defects, RFIs, or punch-list points all burn down naturally. The chart is unit-agnostic; the unit just needs to be countable and meaningful.

Why did the actual line cross the ideal early?

Usually either under-commitment (the team was too conservative) or padded estimates (each item was bigger on paper than in reality). A retrospective should investigate which.

How do I show scope changes?

Use a burn-up: one line for completed work, another for total scope. The gap is what's left; movement in the scope line is what changed.

Which calculators on PMMilestone.org apply to Burn-Down Chart?

For Burn-Down Chart, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.

What is a common misconception about Burn-Down Chart?

That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.

Which related encyclopedia entries should I read alongside Burn-Down Chart?

Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.

How does Dr. Hassan Eliwa's research treat Burn-Down Chart?

Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Burn-Down Chart is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.

How is Burn-Down Chart defined on PMMilestone Research & Insights?

A time-series chart showing remaining work against time, used by agile teams to visualise sprint or release progress and forecast completion. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

Agile · Letter B

Burn-Down Chart

A time-series chart showing remaining work against time, used by agile teams to visualise sprint or release progress and forecast completion.

By Dr. Hassan Eliwa, PhD · Founder of PMMilestone.org and PMMilestone.com · Updated 2026-06-22

Definition

A Burn-Down Chart plots remaining work — usually in story points, hours, or open items — on the vertical axis against time on the horizontal axis. The ideal line trends to zero on the target date; the actual line shows what really happened. Together, they let the team and stakeholders see at a glance whether the sprint or release is on track, and how the team's day-to-day delivery compares with its commitment.

History

The burn-down was popularised by Ken Schwaber in the late 1990s as a Scrum communication tool. It built on earlier lean and TPS visualisations and on the cumulative flow diagrams used in software engineering since the 1980s. Today it sits alongside the burn-up chart, the cumulative flow diagram, and the S-curve as one of the most widely understood progress visuals in project management.

Principles

Remaining, not completed: a burn-down measures what's left, which keeps the team focused on finish.
Updated daily: stale charts mislead more than they inform.
One unit: mix points and hours and the chart loses its meaning.
Visible to everyone: on the team wall or the team dashboard, not buried in a tool.
Honesty over optics: the chart's value is diagnostic; smoothing it defeats the purpose.

Real-World IT / Agile Example

A SaaS team committed to 42 story points in a two-week sprint. By day four, the burn-down was hugging the ideal line. By day seven, it had flattened — a sure sign that work-in-progress was high but completion was not. The team called a "swarm day," paired aggressively on the two oldest stories, and finished the sprint at 38 points. Without the chart, the flatten-out would not have been visible until planning post-mortem.

Real-World Construction Example

On a high-rise fit-out, a similar pattern appears with snag-list burn-down: remaining defects plotted against time to handover. On one tower, the snag burn-down was on track until two weeks before handover, when it flattened at 220 items. The control team investigated and found a single subcontractor responsible for 78% of the open items. Targeted intervention — daily walk-downs, dedicated crew, escalation to the head office — restored the burn-down and saved the handover date.

Burn-Down vs Burn-Up

A burn-down hides scope changes; a burn-up shows them by plotting completed work and total scope on separate lines. For sprints where scope is fixed, burn-down is clearer. For releases where scope evolves, burn-up is more honest — the gap between the two lines tells the scope-creep story.

Project Controls Perspective

Controls leads pair the burn-down with two diagnostics: flatten detection (any day-over-day flat segment longer than two days is a swarm trigger) and velocity reconciliation (the slope of the actual line vs. the team's rolling velocity). On programmes running multiple teams, normalise burn-downs to percentage-remaining so they can be stacked into a single portfolio view.

Common Mistakes

Updating the chart only at the end of the sprint — it becomes a report, not a tool.
Mixing units (hours and story points) so trends are uninterpretable.
Padding estimates to make the actual line hug the ideal — vanity metrics destroy the chart's diagnostic value.
Confusing a flat burn-down with "nothing happening" — usually it means everything is in progress and nothing is done.
Hiding scope changes by silently increasing the starting line; use a burn-up instead.
Showing only sprint burn-downs to executives who care about release dates; pair them with a release burn-up.

Expert Tips

Update daily during stand-up. The act of updating triggers conversation.
Plot the ideal line as a guide, not a target. Real burn-downs are stepped, not straight.
Annotate scope changes on the chart. Honest charts build trust.
Use a burn-up for releases. Scope creep becomes visible.
Watch the last 20%. Most sprints die in the closing days, not the opening ones.

Key Takeaways

The burn-down plots remaining work over time; the diagnostic value is in the shape of the actual line.
Update daily, with one unit, and keep it visible to the team.
Flatten segments are swarm triggers, not noise.
Pair sprint burn-downs with release burn-ups when scope evolves.
Honesty beats optics — a smoothed chart loses its purpose.

Related Concepts

Burn-down charts complement Agile, Kanban, S-curves, KPIs, and Earned Value. Templates at PMMilestone.org.

Frequently Asked Questions

What does a burn-down chart show?
Remaining work on the vertical axis against time on the horizontal axis. The ideal line shows linear progress to zero; the actual line shows how the team really delivered.
Burn-down or burn-up — which is better?
Burn-down is clearer for fixed-scope sprints. Burn-up is more honest for releases where scope changes, because it separates completed work from total scope and exposes scope creep.
How often should I update the chart?
Daily, ideally during the stand-up. A weekly update turns the chart into a report; daily updates make it a conversation.
Why is my burn-down flat?
Almost always because work-in-progress is high but nothing is finishing. Swarm on the oldest item, finish it, then move to the next. Flat segments longer than two days warrant intervention.
Should the burn-down be in hours or story points?
Pick one and stay consistent. Hours work well for sprint-level forecasts; story points are better for cross-sprint velocity comparisons. Mixing the two makes the chart unreadable.
Can I use a burn-down in waterfall projects?
Yes — remaining items, defects, RFIs, or punch-list points all burn down naturally. The chart is unit-agnostic; the unit just needs to be countable and meaningful.
Why did the actual line cross the ideal early?
Usually either under-commitment (the team was too conservative) or padded estimates (each item was bigger on paper than in reality). A retrospective should investigate which.
How do I show scope changes?
Use a burn-up: one line for completed work, another for total scope. The gap is what's left; movement in the scope line is what changed.
Which calculators on PMMilestone.org apply to Burn-Down Chart?
For Burn-Down Chart, the most relevant tools on the flagship platform are the EVM, SPI and CPI calculators on PMMilestone.org. They reproduce the formulas referenced in this entry against your own project data.
What is a common misconception about Burn-Down Chart?
That the topic is well-defined across all references. In practice, definitions vary between PMBOK, PRINCE2, AACE and ISO 21500 — this entry uses the definition most aligned with field practice on capital projects, and flags where the standards diverge.
Which related encyclopedia entries should I read alongside Burn-Down Chart?
Read Earned Value Management, Critical Path Method and the DCMA 14-point assessment next. The full A–Z is available in the PMMilestone Encyclopedia, and quick one-line definitions live in the PM Glossary on the flagship platform.
How does Dr. Hassan Eliwa's research treat Burn-Down Chart?
Dr. Hassan Eliwa's research focuses on owner-side project controls, schedule integrity and forensic delay analysis on capital construction and power programmes. Burn-Down Chart is treated through that lens — what a planning or controls engineer is expected to do with it on a live project, not its textbook definition alone. See the full research library at PMMilestone Research Articles.
How is Burn-Down Chart defined on PMMilestone Research & Insights?
A time-series chart showing remaining work against time, used by agile teams to visualise sprint or release progress and forecast completion. For the full treatment, see the definition, principles, applications and related entries above — every encyclopedia entry follows the same research-grade structure.

View the full FAQ page for Burn-Down Chart →