What is a burndown chart?

A burndown chart plots remaining work against time, visualizing how the workload decreases toward zero. It is a standard tool in Scrum agile development and makes schedule deviations immediately visible.

What is the difference between a burndown chart and a Gantt chart?

A Gantt chart shows tasks with durations and dependencies for planning, while a burndown chart shows remaining workload over time for progress tracking. Using them together gives a multi-angle view of any project.

What should I do if the burndown line is above the ideal line?

A line above the ideal means you are behind. In mid-sprint, check for blockers at daily standup and remove them immediately. Late in the sprint, consider moving some scope to the next sprint or revisiting your Definition of Done to recalibrate velocity.

Burndown Chart Guide: How to Read, Create, and Use It Effectively

"I know what a burndown chart is, but I am not sure how to actually use it." Many teams create burndown charts dutifully without extracting real value from them. The burndown chart is a staple of agile progress tracking, but without a clear understanding of how to read and operate it, it becomes a decoration on the wall. This guide covers the fundamentals and practical application with concrete examples.

What a Burndown Chart Shows

A burndown chart plots the remaining work in a sprint or project over time, showing how the workload "burns down" toward zero. The Y axis represents remaining work (story points, task count, or remaining hours), and the X axis represents dates. Each day, you plot the current remaining amount and connect the dots.

Recommended by the Scrum Guide and widely used beyond Scrum, its strength lies in making "how much is left" instantly visible. For how burndown charts pair with Gantt, see our agile plus Gantt guide.

How to Read a Burndown Chart: Compare Two Lines

The core skill is comparing the ideal line with the actual line:

Ideal line: A straight line from total work at sprint start down to zero at sprint end, assuming constant consumption. For a 10-day sprint with 50 points, it slopes down 5 points per day.
Actual line: Daily plot of actual remaining work. Above the ideal line means behind schedule; below means ahead.

A sustained gap above the ideal line is your first warning sign. A line below the ideal is not always cause for celebration -- it often indicates missed updates or loose "done" definitions.

Four Common Burndown Patterns

Smooth steady decline: Healthy progress. Tasks are closing on schedule.
Flat first half, cliff at the end: Completions are reported in bulk at the end. Your Definition of Done is probably ambiguous.
Spike upward mid-sprint: Scope was added. Time to renegotiate priorities.
Parallel gap that never closes: Velocity estimation is wrong. Adjust planned capacity next sprint.

How to Build a Burndown Chart: 5 Steps

Step 1: Choose Your Unit

Story points: The agile standard, using relative estimation.
Task count: Simplest to run, but accuracy drops when tasks vary in size.
Remaining hours: Precise but expensive to maintain.

Pick one and stick with it. Switching mid-flight destroys historical comparability.

Step 2: Plot the Total and Draw the Ideal Line

The total work at sprint start defines the Y-axis max. Draw a straight line from that point down to zero at sprint end. Dividing by working days gives you the daily burn pace.

Step 3: Update Actuals Daily

After each daily standup, team members report remaining work and the chart is updated. Making this a fixed standup ritual keeps the data fresh.

Step 4: Act on Anomalies Immediately

When the gap between actual and ideal persists for two or more days, do not wait for the sprint review. Diagnose the cause, remove blockers, and adjust scope or support. For delay root causes, see our project delay guide.

Step 5: Debrief at the Retrospective

At sprint retro, examine the burndown shape. Questions like "why was the first half flat?" and "which day did the gap open?" produce concrete improvements for the next sprint.

Common Burndown Mistakes

Ambiguous "done" definition: Counting "almost finished" tasks causes the line to drop and bounce back.
Weekly updates instead of daily: Late detection equals late response.
Inconsistent story point scale: If "3 points" means something different each week, the line is meaningless.
Watching only the actual line: The whole point is the gap with the ideal line.

Burndown vs Burnup

The burnup chart tracks completed work climbing upward. It excels at showing scope changes (the total line moves). Burndown is simpler; burnup handles shifting scope better. Many teams use both.

Combining with a Gantt Chart

A burndown chart shows "how much is left." A Gantt chart shows "how it all fits together." Neither alone tells the full story. Use burndown for daily sprint tracking and Gantt for quarterly overview. For Gantt fundamentals, see our Gantt chart basics and milestone tips.

Burndown-Style Tracking in Ganty

Ganty is Gantt-based, but by combining task progress percentages with remaining days you can approximate burndown tracking. Filtering to the critical path reveals remaining risk at a glance -- particularly useful for hybrid agile-waterfall teams. Start with the free plan today.