Using working days in a SAFe Planning Increment

A Planning Increment has a calendar boundary, but its useful capacity depends on people, location, leave, focus, dependencies, and historical delivery behavior.

What the calendar contributes

The calendar tells a team how many weekdays remain after weekends and the selected public-holiday assumptions. For a distributed Agile Release Train, comparing calendars can reveal why teams have different nominal opportunity during the same increment.

A practical PI worksheet

  1. Enter the PI start and end dates, including whether your organization treats the final day as available.
  2. Add each team rather than combining countries into one average.
  3. Enter team size, average availability, and focus factor.
  4. Review the shared delivery days and core-hours overlap.
  5. Record exceptions such as iteration boundaries, planned maintenance, training, and company holidays.
  6. Compare the adjusted person-day estimate with that team’s recent capacity and velocity history.

Story points stay team-specific

SAFe planning may use story points and capacity allocation, but this calculator does not define a universal story-point conversion. A historical ratio can be entered as an optional planning aid, but it should come from the same team and a comparable period. It should not be used to compare one team’s productivity with another’s.

Do not hide uncertainty: a lower capacity estimate can be a useful planning signal. It may indicate a holiday, leave, support load, or coordination constraint that should be discussed before commitment.

Example discussion

If an India team loses Gandhi Jayanti during an October increment while a U.S. team loses a different weekday to a federal holiday, the teams do not have identical calendar capacity. The difference is not evidence that one team is less productive; it is a scheduling fact to account for.

Try the distributed team capacity planner and save the assumptions with the plan. For official SAFe terminology and current framework guidance, consult the Scaled Agile Framework reference site. Last reviewed: October 2026.