Burndown

A burndown chart plots remaining work, measured in hours or story points, against elapsed time in a project or sprint, showing at a glance whether delivery is on pace to finish on time. As work is completed, the line burns down toward zero. Divergence from the ideal line is an early warning of overrun or scope removal.

Reading a burndown chart

y-axis: Remaining work (hours or story points)
x-axis: Time (days, weeks, or sprint length)
Ideal line: Straight diagonal from total scope at start to zero at end date
Actual line: Where the project stands today

• Actual line above ideal: behind pace, at risk of overrun
• Actual line at ideal: on track
• Actual line below ideal: ahead of pace, or scope was removed
• Flat actual line: work stopped, or time entries are not being logged

A flat line that persists for more than a few days is one of the clearest signals of a delivery problem. It indicates either a real blocker or a gap in time tracking discipline.

Burndown in professional services vs. agile software teams

Agile software teams use burndown at the sprint level, tracking story points over a two-week cycle. Professional services firms typically use it at two levels:

1. Phase or sprint burndown: tasks remaining in the current delivery phase
2. Project budget burndown: hours remaining against the total contracted budget

The second is more important for services firms because it connects directly to project profitability. A project that has consumed 80% of its contracted hours at the 60% delivery mark is heading toward a delivery overrun unless scope is reduced or a change order is signed.

Scope changes break the chart

When scope is added mid-project, the total remaining work line resets upward. When scope is removed, it resets downward. A burndown chart without scope change annotations is misleading: unexplained jumps in the line look like lost work or sudden acceleration. Always mark scope changes so the chart reflects intentional adjustments.

A project plan should be updated in parallel with any scope change so that both the schedule and the burndown baseline stay consistent.

Burndown vs. burn rate

Burndown and budget burn are related but distinct:

• Burndown tracks remaining work: what is left to do
• Burn rate tracks consumed budget: how much has been spent

A project can be burning budget quickly while burning scope slowly, which is a clear sign of an efficiency or staffing-mix problem. Running both charts together gives a more complete picture of project health than either one alone.