Sprint burndown calculator

This sprint burndown calculator turns the current state of an iteration into one practical planning number: the story points that must be completed per remaining day to finish on time. Enter the original sprint commitment, elapsed days, remaining days, and completed points. The result shows both the unfinished workload and the required daily velocity, making it easy to compare the recovery pace with what the team can realistically deliver before the sprint ends.

Turn a burndown snapshot into a clear daily target

A burndown chart shows direction, but a chart alone does not always answer the question a team faces during a daily review: how quickly must the remaining work move now? This calculator starts with the sprint's total story points and subtracts the points already completed. It then divides that unfinished amount by the number of days still available.

The resulting required daily velocity is a forward-looking target, expressed in story points per remaining day. For example, a sprint with substantial work left and only a few days available will produce a high target immediately, without relying on visual interpretation of a trend line. Include every elapsed day in the elapsed-days field, even when no points were finished, so the snapshot remains an honest description of the calendar.

The elapsed value is returned for context, while the deadline calculation uses the remaining days because those are the opportunities the team still has to complete work. Use the number as a planning signal, not as an individual productivity quota.

Interpret required velocity with delivery context

The required daily velocity tells you the arithmetic pace needed to burn the remaining estimate by the deadline. Compare it with the team's typical completed story points per day, recent throughput, current work in progress, and known impediments. If the target is comfortably below a sustainable pace, the sprint remains arithmetically achievable.

If it is far above that pace, the useful response is not to pressure people to inflate output. Instead, examine whether a blocked item can be unblocked, whether stories can be split while preserving valuable outcomes, or whether scope should be renegotiated with the product owner. A result of zero means all committed points are already complete, so no further daily velocity is required.

Fractional results are normal: they represent an average over the days remaining, not a demand to complete part of a story every day. Story points are team-relative estimates, so the figure should only be compared with evidence from the same team and estimation practice rather than with another team's velocity.

Use consistent inputs and handle the deadline boundary

Keep the units consistent across every input. Total and completed work must both use story points from the same sprint baseline, while elapsed and remaining time should both use the same definition of a day, usually planned working days rather than calendar days. Update completed points according to the team's shared definition of done; counting partially finished work makes the remaining estimate look smaller without creating a deliverable increment.

The calculator rejects completed points above the original total because that combination cannot describe remaining work against the supplied commitment. It also rejects negative values, non-finite numbers, and fractional day counts. Most importantly, zero remaining days is an error: once no days remain, division cannot produce a meaningful required daily pace.

At that boundary, review the sprint outcome directly instead of treating an infinite or undefined number as guidance.