Calculation methodology and limitations
How Sprint Capacity Planner calculates points, handles weekdays and PTO, checks risks, and stores your workspace.
Member-based capacity
For each active member: baseline points × available days ÷ capacity days × multiplier. Available days are capacity days minus PTO, clamped to zero. Inactive members contribute zero. A sprint with no capacity days contributes zero. Displayed points round to one decimal; calculations retain precision.
New plans created in this version use the count of Monday–Friday days between the inclusive sprint dates. Sprint length is entered in calendar days: 14 represents two weeks. Holidays are entered manually as time off. Weekends are not working days in this model.
Saved-plan compatibility
Older saved plans and the original demo retain their calendar-day denominator and display a legacy notice. Their dates, baselines, and results are not silently migrated. Create a new plan to use weekday-based adjustments. Set baseline points for the chosen sprint length; the app does not scale baselines automatically when duration changes.
Other velocity modes
Team-average mode repeats the supplied value. Sprint-specific mode uses each sprint’s supplied value. These are final capacities: PTO and multipliers do not reduce them again. Availability still informs risk and recommendation checks.
Risk checks
The app checks over-commitment, missing required skills, single-person dependencies, PTO conflicts, and weak cross-training coverage. Working, strong, and expert count as qualified skill coverage. Strong and expert count as advanced coverage. These are rules based on your entries, not independently verified assessments.
Planned points above capacity produce an over-commitment warning. The severity increases above 110% and above 125%; exact boundaries use the lower band. Zero capacity with planned work is critical. Cross-training suggestions consider available capacity and related skills, and can abstain when no candidate qualifies.
Import, export, and local storage
CSV imports map weekday PTO dates into a selected plan. Avoid overlapping ranges. The workspace retains counts, not original absence dates. Export reconstructs dates as the first weekdays of each sprint and includes team information and skills; it does not back up full plans, work items, or risk acknowledgements.
Print a plan summary to retain a readable record. Workspace data uses versioned browser local storage, which does not sync across devices and may be unavailable or cleared. The application includes automated tests for calculation, date, risk, CSV, and storage behavior, but your team should still check the inputs and results.
Use the result as a planning input
Points are specific to your team’s estimation scale. They are not hours, individual performance scores, or a guaranteed delivery commitment. This tool does not fetch public holidays, measure historical velocity, sync work trackers, or automatically reserve training time.