Sprint Capacity Planner

Sprint capacity planning with PTO and holidays

Account for unavailable weekdays, partial allocation, and holidays without subtracting the same absence twice.

Establish the dates first

New plans use calendar dates for sprint boundaries and Monday–Friday days for member-based capacity adjustments. A 14-calendar-day sprint normally has 10 weekdays. Public holidays are not detected automatically: count an unavailable holiday as PTO for each affected teammate.

Use one adjustment for each absence

For a 10-weekday sprint, a member with 20 baseline points and three unavailable weekdays contributes 20 × 7 / 10 = 14 points with multiplier 1. If that person is also allocated half-time to this work during the remaining days, a 0.5 multiplier yields 7 points. Do not apply the multiplier for an absence already entered as PTO.

A baseline should describe a full sprint under the assumptions you state. For a person whose baseline already includes their normal reduced schedule, only apply additional adjustments when their availability changes.

Import dated leave

  1. Create the plan with the correct start date and sprint duration.
  2. Put leave dates in the CSV template’s pto_dates column, using YYYY-MM-DD:YYYY-MM-DD for an inclusive range.
  3. Import the file, review warnings, and select the plan for weekday PTO mapping.
  4. Review each sprint’s resulting day counts before planning work.

Separate ranges with semicolons and avoid overlapping ranges. Imports create or update teammates by name. If you import before creating a plan, import again after the plan exists to map leave dates.

Understand the limits

The workspace stores PTO counts per sprint, not the original leave dates. Export reconstructs dates using the first weekdays of the selected sprint. Do not use that export as an authoritative leave calendar. Nonstandard working weeks need a separate availability calculation; in sprint-specific mode you can enter the final result yourself.

Legacy plans retain their old calendar-day denominator and display a notice. Creating a new plan uses weekday adjustment without rewriting your history. Team-average and sprint-specific capacity values do not automatically decrease when PTO changes.

Look beyond reduced totals

When the only qualified specialist is away, reducing total points alone may not resolve the problem. Re-scope the work, move it, or arrange qualified coverage. Follow the skills-matrix workflow and download the team CSV template.