Sprint Burndown Progress

Burndown tracks unfinished committed work. Ideal burndown charts also plot against calendar days; this calculator gives the current remaining share instantly.

Remaining % = (remaining ÷ planned) × 100; completion % = 100 − remaining %.

Tip: Keep “Remaining Work” and “Planned Sprint Work” on the same basis (units, period, and definition) before you calculate.

Cluster: Software Testing hub · Professional KPIs · Percentage guide

Burndown progress shows how much planned sprint work is still left.

Enter remaining points (or tasks) and the original planned commitment for the sprint.

Points or tasks still not done
Original (or re-baselined) sprint commitment

Remaining Work %

Understanding Sprint Burndown Progress

How we calculate. Remaining % = (remaining ÷ planned) × 100; completion % = 100 − remaining %. See our methodology and accuracy policy .

Real-world scenario: A typical Sprint Burndown Progress case uses remaining work 12 and planned sprint work 40. Enter the same figures below to reproduce the worked path.

What is Sprint Burndown Progress?

Burndown tracks unfinished committed work. Ideal burndown charts also plot against calendar days; this calculator gives the current remaining share instantly.

  • Remaining should use the same unit as planned (points or tasks)
  • Scope adds raise planned mid-sprint—note them explicitly
  • QA burndown can track open test cases the same way

The Formula

Sprint Burndown Remaining
Remaining % = (Remaining work ÷ Planned work) × 100

Worked Example

Scenario: The sprint committed 40 points. 12 points remain unfinished.
Step 1: Remaining = 12
Step 2: Planned = 40
Step 3: (12 ÷ 40) × 100 = 30% remaining (70% complete)
Answer: Your score is 333.3% (verified with this calculator).

Common Use Cases

  • Daily standup: share remaining % at a glance
  • Mid-sprint risk: flag when remaining stays high late in the sprint
  • QA packs: burndown open regression cases

Pro Tips

  • Re-baseline planned if product owners add committed scope
  • Blocked work still counts as remaining until done or descoped
  • Pair with burnup when scope is growing
ScenarioWhen to use
Percent of a numberFinding a part of a whole (tax, tip, score)
Percent changeComparing old vs new values

Limitations: Sprint Burndown Progress results are planning aids for Agile/QA teams—not contractual delivery commitments. Confirm definitions with your scrum/quality playbook.

Common mistakes

  • Swapping part and whole: The denominator must be the full total, not a subset.
  • Rounding too early: Carry extra decimal places through multi-step work before rounding the final percent.
  • Mixing percent and decimal forms: Enter rates in the format the calculator labels expect.

When to use this calculator

  • Use this page when your wording matches sprint burndown and the form labels on screen.
  • Use percent of a number for “what is X% of Y?” problems.
  • Use number is what percent when you know part and whole and need the percent.

Still unsure about sprint burndown? Start with the quick answer above, then open the linked calculator that matches your wording.

Frequently Asked Questions

How do I use this sprint burndown calculator?

For sprint burndown, enter the values labeled on the form, then press Calculate. Compare the result to the worked example on this page.

What formula does this page use?

See the quick answer and formula box above for sprint burndown—the same percentage calculator expression is applied to your inputs.

What if my result looks wrong?

When checking sprint burndown, re-check part vs whole (or rate vs base), rounding, and whether percents were entered as 25 rather than 0.25 when the form expects percents.

Authoritative References

For Agile and software testing practices, consult: