Burndown Chart Calculator

Use this burndown chart calculator to check whether a sprint or fixed-scope delivery plan is ahead, on track, or at risk before changing scope or dates.

Planning estimate

Live calculator

Burndown chart calculator

StatusAt risk

100 work units remain versus 88 on the ideal line.

Remaining work100

Adjusted scope minus completed work.

Projected finishDay 11

20 units per elapsed day so far.

Sprint burndown summary

Use one fixed unit definition such as story points, hours, tasks, or tickets for the whole sprint snapshot.

Burndown measureValue
Adjusted scope220
Completed work120
Actual remaining work100
Ideal remaining work today88
Variance vs ideal12
Current burn rate/day20
Required burn rate/day25
Remaining days4
Planning note

Burndown is a progress signal, not an individual performance score. Scope changes, batch updates, blocked work, and estimate changes can move the line without proving the team is faster or slower.

Planning comparison only. Check estimates, omitted costs, timing, and constraints before making an operating decision.

Formula

Burndown chart formula

Remaining work = adjusted scope - completed work; ideal remaining = adjusted scope x (1 - days elapsed / sprint days)

Use one consistent work unit such as story points, hours, tasks, or tickets. Scope changes should be tracked separately from completed work.

How to use

Steps

  1. Enter the planned work at the start of the sprint or delivery timebox.
  2. Enter approved scope added separately so the original baseline stays visible.
  3. Enter completed work, sprint duration, and elapsed working days.
  4. Compare actual remaining work with the ideal line and required burn rate before changing commitments.

Example

Sample calculation

Planned work200 points
Scope added20 points
Completed work120 points by day 6
StatusAt risk; projected finish day 11.0

Calculator use

Best for

  • Pricing, runway, cash flow, or work assumptions before an operating decision.
  • Base, conservative, and optimistic cases with visible inputs.

Before relying on it

Check first

  • Use one consistent work unit such as story points, hours, tasks, or tickets. Scope changes should be tracked separately from completed work.
  • Mixing scenarios, units, or time periods in one comparison.
  • Leaving out material costs, capacity limits, uncertainty, or dependencies.

Details

What to know before using the result

Ideal lineAdjusted scope to zero

The ideal line is a simple reference path, not a guarantee or performance target by itself.

VarianceActual remaining minus ideal remaining

Positive variance means more work remains than the ideal line expects at this point.

Decision boundaryProgress signal

Use burndown with blockers, scope changes, batch updates, and quality risk before compressing a schedule.

Benchmarks

How to read the result

Actual remaining: Adjusted scope - completed work.

The main status number for the current sprint snapshot.

Ideal remaining: Adjusted scope x remaining time share.

A straight-line reference for reading whether the sprint is ahead or behind pace.

Required burn rate: Actual remaining / remaining days.

Useful for deciding whether scope, staffing, or date assumptions need a realistic adjustment.

Calculator accuracy

Methodology and assumptions

Formula, inputs, limitations and review record
Formula

Remaining work = adjusted scope - completed work; ideal remaining = adjusted scope x (1 - days elapsed / sprint days)

Inputs used

Planned work, Scope added, Completed work, Sprint days, Days elapsed

Limitations

Business results depend on contracts, accounting treatment, taxes, payment timing, refunds, collections, and operating assumptions.

Review record

Catalog QA baseline on June 6, 2026. This date marks the catalog-wide automated and editorial QA baseline, not a tool-specific expert review.

Cite this page

Toolkit Shelf. Burndown Chart Calculator. https://toolkitshelf.com/tools/burndown-chart-calculator

FAQ

Common questions

Does a burndown chart measure individual performance?

No. It is a team progress signal for remaining work over time. It should not be used as an individual performance score.

What happens when scope changes during the sprint?

Track scope added separately. Otherwise a rising remaining-work line can be mistaken for poor execution when the real cause is new work.

Why can a burndown chart look worse than reality?

Late status updates, batch-closing tickets, blocked review work, and estimate changes can all distort the line. Use it with delivery context.