How do you calculate team capacity in SAFe?
In SAFe, a team's capacity for an iteration is computed from each member's available working days (leave, holidays, and events deducted), converted into points through the team's observed velocity. PI capacity is the sum of the iterations' capacities, adjusted for the innovation and planning share. Teams then commit during PI Planning to that capacity, not to a theoretical figure.
SAFe and capacity: planning the capacity of an agile release train
Sustainable PI commitments come from computed capacity, not assumed capacity.
Last updated :
Calculation steps
- Count available days per person over the iteration, absences deducted.
- Apply the average observed velocity (points per available day).
- Remove the share spent on run work, innovation, and planning.
- Add up the iterations to get PI capacity.
Common mistakes
- Committing to gross capacity and forgetting absences and run work.
- Counting a shared person at 100% in each team.
- Not revising velocity after several iterations.
- Ignoring dependencies that move workload from one team to another.
Indicators
| Indicator | Definition |
|---|---|
| Iteration capacity | Available days × velocity per day, after run work. |
| PI predictability | Share of PI objectives achieved against objectives committed. |
| Shared people | Number of members split across several teams. |
FAQ
Does Workload replace Jira Align?
No. Workload is a capacity and programs layer; detailed delivery planning stays in your agile tools.
How do you handle a person shared between two teams?
By splitting their capacity between the teams (for example 60/40) rather than counting them twice.
What is the ART?
The Agile Release Train, a group of teams that plan and deliver together on the PI cadence.
Go further
Explore more
From theory to your workload plan
Import your teams and projects as CSV and see capacity and overload in half an hour.
14-day free trial