Free Agile tool

Forecast Burndown

Estimate Sprint completion from the current task distribution and observed delivery pace.

Forecast your Sprint completion

Update the current Sprint snapshot and see every result recalculate immediately.

Prefer Portuguese? Use esta ferramenta em português.

Forecast Burndown versus a traditional Sprint Burndown

A Burndown Chart shows how much work remains across the Sprint using historical daily values. This Forecast Burndown starts from the current Sprint snapshot and observed velocity to estimate when the remaining task count may reach zero.

How the tool works

Enter the total number of Sprint tasks, the Sprint duration, and the current day. Distribute every task across your ordered workflow stages, then choose the stage from which work counts as complete. The calculator compares actual progress with a linear ideal and projects completion using completed tasks per elapsed day.

Supported input and output

This version works with whole task counts and whole Sprint days. Stage names are free-form, stages can be added, removed, edited, and reordered, and the selected completion stage plus every later stage counts toward completed work. The distributed total must match the Sprint total before calculated results appear.

Practical example

In a 20-day Sprint with 40 tasks, 17 completed tasks on day 12 produce an observed pace of about 1.42 tasks per day. At that pace, completion is projected near day 28, around eight days after the planned Sprint finish.

Common use cases

Use the Forecast Burndown during a stand-up, Sprint review, delivery check, or planning conversation to make current progress visible and discuss whether scope, capacity, or priorities need attention. Custom workflow stages support teams whose definition of done begins at review, testing, deployment, or another point.

Limits and important checks

This is a linear estimate, not a guarantee. It treats tasks as equal units, uses no daily history, and cannot account for blockers, weekends, changing scope, uneven task size, or future changes in team capacity. Use the projection as a conversation aid alongside team context.

Privacy and local processing

Unless the tool explicitly identifies an external lookup, input and generated output are processed in your browser and are not uploaded to CosmoTools. Avoid placing secrets in any web page and review downloaded results before using them in production.

Frequently asked questions

How is the Sprint forecast calculated?

The tool divides completed tasks by the current Sprint day, then projects that observed average pace until all tasks are complete.

Which tasks count as complete?

You choose a completion stage. Tasks in that stage and every later stage in the ordered workflow count as complete.

Is this the same as a historical burndown chart?

No. This first version uses the current Sprint snapshot and a linear projection rather than a history of daily remaining work.

Is the forecast a guarantee?

No. It is an estimate based on the average pace observed so far. Scope, blockers, task size, and team capacity can change the outcome.

Are my Sprint values uploaded?

No. Calculations and storage remain in your browser.