Purpose and scope
What this timeline establishes
Project when remaining sprint work will finish at the observed delivery rate.
The Sprint Burndown Finish-Date Forecaster creates checkpoints from Sprint starts, Sprint ends, Starting points, Points completed, and Elapsed workdays; Save Elapsed workdays separate from internal buffers.
Instructions
How to use this calculator
Confirm Sprint starts and Sprint ends as the Sprint Burndown Finish-Date Forecaster control point, then save Starting points, Points completed, and Elapsed workdays tied to the applicable reference data.
- Confirm Sprint starts and Sprint ends as the controlling Sprint Burndown Finish-Date Forecaster constraint.
- Confirm Starting points, Points completed, and Elapsed workdays from the applicable reference data.
- Create the Sprint Burndown Finish-Date Forecaster checkpoints, then trace Elapsed workdays in chronological order.
- Isolate Elapsed workdays in a second Sprint Burndown Finish-Date Forecaster run to identify any boundary or rounding effect.
Calculation
Method used
Observed points per elapsed workday are extended across remaining points to estimate a finish date.
The Sprint Burndown Finish-Date Forecaster applies Sprint starts, Sprint ends, and Starting points in sequence; trace the Elapsed workdays allowance at each checkpoint.
Calculation method last reviewed: June 21, 2026.
Visual audit
Reading the calculated timeline
The Sprint Burndown Finish-Date Forecaster timeline creates checkpoints from Sprint starts, Sprint ends, Starting points, Points completed, and Elapsed workdays. Trace Elapsed workdays from the anchor toward the constraint carrying the consequence.
Interpretation
Interpreting the calculated date and buffers
The projection assumes the observed rate continues and does not model end-of-sprint testing or scope movement.
Trace the Sprint Burndown Finish-Date Forecaster deadline separately from Elapsed workdays; internal buffers remain adjustable unless the reference data fixes them.
The Sprint Burndown Finish-Date Forecaster handles this calculation; the Sprint Capacity Calendar can then convert sprint length, team size, leave, and focus factor into delivery capacity.
Worked scenario
Example calculation
Evaluate the Sprint Burndown Finish-Date Forecaster control event with Sprint starts and Sprint ends, then trace each Elapsed workdays adjustment.
Boundaries
Important edge cases and limitations
Point scope, weekend work, carryover, blocked items, and nonlinear completion patterns are excluded.
Replace the Sprint Burndown Finish-Date Forecaster allowance when Elapsed workdays differs from the reference data rule; create its dependent checkpoints again.
Practical use
Recommended workflow
Update the forecast after scope or completion changes and compare it with remaining calendar capacity.
Input audit
Checklist for this calculation
- Trace the Sprint Burndown Finish-Date Forecaster control point in Sprint starts and Sprint ends.
- Save Elapsed workdays separate from discretionary buffers.
- Evaluate the earliest Sprint Burndown Finish-Date Forecaster checkpoint with its constraint.
- Save Starting points, Points completed, and Elapsed workdays beside the Sprint Burndown Finish-Date Forecaster; include Elapsed workdays in any saved or shared record.
Questions
Frequently asked questions
Why can a sprint look on track early and finish late?
Work is not always completed evenly; testing, integration, and blocked items can concentrate near the end.
Why is Elapsed workdays worth testing separately in the
Create the Sprint Burndown Finish-Date Forecaster with a second Elapsed workdays value, then evaluate checkpoints from Sprint starts outward. The changed Elapsed workdays identifies the allowance moving the constraint.
Should Sprint starts or Elapsed workdays control the sprint burndown finish-date forecaster timeline?
Confirm Sprint starts as the Sprint Burndown Finish-Date Forecaster control point, then trace Elapsed workdays separately. Save Sprint Burndown Finish-Date Forecaster Elapsed workdays reminders provisional unless the reference data fixes their timing.
Which sprint burndown finish-date forecaster assumptions should travel with the output?
Save Sprint starts and Sprint ends with the Sprint Burndown Finish-Date Forecaster output, then note Starting points, Points completed, and Elapsed workdays and the calculation date so the result can be reproduced.