Purpose
Frame the time problem correctly
Convert sprint length, team size, leave, and focus factor into delivery capacity.
The Sprint Capacity Calendar addresses sprint capacity: it is designed to convert sprint length, team size, leave, and focus factor into delivery capacity. For the question at hand, define the particular contract, project, invoice, workflow, or reporting period; a date borrowed from one case and a duration borrowed from another can still produce a plausible but irrelevant answer.
At the definition stage, the practical scope of sprint capacity is deliberately narrower than the surrounding operational decision. For sprint capacity, a throughput-based forecast is conditional on the historical sample, work-in-progress policy, and future item mix. Before interpreting a date, treat Sprint starts as the anchor and keep Delivery focus (%) tied to that same source scenario.
Keep this calculation distinct from the Project Milestone Scheduler, used to turn ordered milestone durations into a dated project timeline.
Input review
Input quality matters more than extra decimals
While checking the entries, the sprint capacity calculation draws on Sprint starts, Sprint length (weeks), Team members, and 3 additional fields. For the entered case, capture the sprint capacity entries from one source version before experimenting with alternatives. For the documented baseline, retain the zone of each timestamp, the calendar convention for every date, and the stated unit of each duration or percentage.
- Sprint starts for sprint capacity: Choose Sprint starts from the relevant dated record rather than from a later estimate.
- Sprint length (weeks) for sprint capacity: Enter Sprint length (weeks) in weeks and keep that unit consistent with the other duration fields.
- Team members for sprint capacity: Enter the recorded numeric value for Team members and retain its stated unit with the result.
- Hours per workday for sprint capacity: Record Hours per workday as hours from the source schedule or measurement.
- At source review, total team leave days for sprint capacity: Enter Total team leave days in days and keep that unit consistent with the other duration fields.
- Delivery focus (%) for sprint capacity: Enter the recorded numeric value for Delivery focus (%) and retain its stated unit with the result.
For the entered case, read Sprint starts together with Delivery focus (%) rather than validating each field in isolation. For the documented baseline, a correct-looking number can describe the wrong case when an anchor is transposed, a duration changes units, or an exclusion belongs to another calendar.
Method
The rule used by this calculator
Weekday person-hours are calculated first, leave is removed, and the focus factor reserves capacity for meetings, support, and other non-delivery work.
In the unrounded work, connect each displayed operation to its named field. At the equation review, preserve unrounded intermediate values for sprint capacity; if the result represents complete days, stages, cycles, or work items, decide whether the real planning rule permits a fraction or requires a stated rounding convention.
At the unit check, a useful sprint capacity arithmetic check holds every entry constant except Delivery focus (%). While tracing the arithmetic, the revised sprint capacity output should move in a direction that agrees with the role of that field; an unexpected movement usually points to a unit, sign, or boundary mistake.
Verification
Independent checks for the schedule
At the audit step, review the sprint capacity result independently of the calculate button. At the source reconciliation, use the source record to estimate direction and scale, then compare that expectation with the displayed date, duration, path, capacity, or bucket.
- Before publication, reconcile Sprint starts with the source record before calculating.
- In a separate review, verify the unit and meaning of Sprint length (weeks) rather than relying on its numeric size.
- A separate sprint capacity check should keep completed work, remaining work, and parallel capacity on the same measurement basis.
- At the source reconciliation, change Delivery focus (%) by one controlled increment and confirm the sprint capacity result moves in the expected direction.
- Before accepting sprint capacity, compare the forecast with several recent periods instead of relying on one favorable observation.
For the manual reasonableness test, if a sprint capacity check fails, preserve the entered case instead of forcing the answer to match. As an independent check, identify the sprint capacity assumption that differs from the source and rerun the Sprint Capacity Calendar only after correcting that field.
Understanding the output hierarchy
Interpretation Use delivery hours for planning work, not gross attendance hours. Historical velocity remains the stronger guide when available. Validate Sprint starts, Sprint length (weeks), and Team members beside the Sprint Capacity Calendar headline; Delivery focus (%) reveals rounding across the underlying totals.
The Sprint Capacity Calendar dashboard places underlying totals beside Sprint starts, Sprint length (weeks), Team members, Hours per workday, Total team leave days, and Delivery focus (%). Validate Delivery focus (%) in its original unit before accepting the underlying totals or headline status.
When explaining the output, describe the answer as a sprint capacity result and name its time basis, anchor, and governing scenario. When the answer is reported, this prevents the sprint capacity figure from being mistaken for an approval, compliance finding, entitlement, or delivery guarantee.
Work through the default scenario
Worked scenario Example: A six-person, two-week sprint begins with sixty person-days before leave. Multiplying usable hours by a 70-percent focus factor creates a more realistic commitment ceiling. Cross-check Delivery focus (%) with the Sprint Capacity Calendar underlying totals before judging the Delivery focus (%) headline scale or units.
For the demonstration values, rebuild the sprint capacity example once with the published defaults. For a fresh sample run, write down the anchor, the intermediate relationship, and the output unit; then alter a single entry so the reason for the changed answer remains visible.
The worked sprint capacity case demonstrates how to convert sprint length, team size, leave, and focus factor into delivery capacity, but it is not a ready-made project or deadline. While reproducing the example, replace every sprint capacity sample value with the actual record before using the Sprint Capacity Calendar result in a schedule, notice, forecast, or approval workflow.
Make a later rerun possible
For the next reviewer, a later reviewer should be able to reproduce the sprint capacity result without guessing. Store these items with the output:
- Sprint starts
- Sprint length (weeks)
- Team members
When preserving the case, also retain the calculation timestamp and the version of any calendar, dependency list, policy, or workflow assumption used. At the documentation step, mark superseded sprint capacity runs as historical instead of silently replacing them.
Workflow
An operational use for the result
Practical use Compare calculated capacity with the previous several sprints and choose the lower defensible commitment.
The practical use of this page is to convert sprint length, team size, leave, and focus factor into delivery capacity. In the downstream process, keep the sprint capacity result beside the contract, project plan, work-item history, invoice, calendar, or approval record it informs so its assumptions remain visible.
For a revised schedule, when Sprint starts or Delivery focus (%) changes, save a new sprint capacity run rather than overwriting the old one. At the decision handoff, a side-by-side sprint capacity comparison then shows whether the changed conclusion came from the anchor, a duration, an exclusion, or a policy decision.
Before the next reporting period
Before publishing the Sprint Capacity Calendar result, identify who owns its source data, who may approve an exception, and when that source will next change. Clear ownership matters because the sprint capacity assumptions may become outdated before the surrounding workflow is complete.
Keep the original Sprint starts and Delivery focus (%) beside any revised sprint capacity case. In the Sprint Capacity Calendar handoff, state which entry changed, why it changed, and whether the scheduling or deadline conclusion changed with it.
Finish by comparing the calculated sprint capacity output with one observable fact from the same workflow: a known milestone, a filed notice, a recent throughput measure, an invoice date, or an approved calendar checkpoint. For sprint capacity, this comparison is a reasonableness test rather than a replacement formula.
Boundaries
What still requires policy or human judgment
Holidays, individual skills, part-time schedules, carryover, and unplanned support incidents require explicit adjustment. Refresh Delivery focus (%) in the Sprint Capacity Calendar before reading the underlying totals or headline.
For policy-controlled treatment, use the Sprint Capacity Calendar as transparent sprint capacity arithmetic, not as a substitute for the controlling agreement, approved project plan, official calendar, financial record, or responsible reviewer. For an unmodeled exception, resolve material sprint capacity discrepancies before distributing the result.
Before relying on Sprint Capacity Calendar
Is focus factor the same as productivity?
No. It represents the share of scheduled time available for planned delivery, not how efficiently people perform during that time.
Can an error in Sprint starts shift the sprint capacity calendar output?
Cross-check Sprint starts with Delivery focus (%) inside the Sprint Capacity Calendar reporting basis. Hold the Delivery focus (%) unit aligned with the Sprint starts period before reading the headline.
Which sprint capacity calendar output is most affected by?
Hold Sprint starts and Sprint length (weeks) unchanged and refresh Delivery focus (%) once in the Sprint Capacity Calendar. Cross-check the Delivery focus (%) component with underlying totals to identify a proportional or threshold effect.
How does Delivery focus (%) qualify the sprint capacity calendar headline?
The Sprint Capacity Calendar headline compresses Sprint starts and Sprint length (weeks), so cross-check it with Delivery focus (%) and underlying totals. The Delivery focus (%) denominator then exposes rounding in the Sprint Capacity Calendar.