Calculating SAFe PI capacity and tracking it through to actuals
Updated on · Capalane
In short. PI capacity is prepared iteration by iteration: each person's working days, minus public holidays and leave, multiplied by their allocation to the train. SAFe proposes normalized points (8 per person per iteration, minus one per day of absence) for planning; the budget is tracked in days. During the PI, compare time logged with planned capacity every week.
At PI planning, each team commits to objectives that match its capacity. If capacity is overestimated (forgotten holidays, summer leave not deducted, people shared between two trains), objectives are missed, and trust in the next PI planning erodes.
The structure of a PI
A Program Increment (PI) usually lasts 8 to 12 weeks. The most common case: five two-week iterations, four for development and a final Innovation and Planning (IP) iteration, which also hosts the next PI planning.
Capacity is therefore calculated per iteration first, then added up over the PI: that is where holidays and leave fall.
SAFe normalized story points
For teams without velocity history yet, SAFe proposes a convention:
- 8 points per full-time developer or tester per two-week iteration (ten days, minus two days of work outside stories);
- minus 1 point per day of leave or public holiday for each member;
- pro rata for part-time or shared people.
This convention gives every team on the train a common baseline. Once real velocity is known, after two or three iterations, it replaces the convention.
Example: a team of five over one iteration
Iteration from 4 to 15 May 2026, team in France: ten weekdays, two of them public holidays (Friday 8 May and Thursday 14 May).
| Member | Allocation to the train | Leave | Days available | Normalized points |
|---|---|---|---|---|
| Developer 1 | 100% | 0 | 10 − 2 = 8 | 8 − 2 = 6 |
| Developer 2 | 100% | 3 | 10 − 2 − 3 = 5 | 8 − 5 = 3 |
| Developer 3 | 50% | 0 | (10 − 2) × 0.5 = 4 | (8 − 2) × 0.5 = 3 |
| Tester 1 | 100% | 1 | 10 − 2 − 1 = 7 | 8 − 3 = 5 |
| Tester 2 | 100% | 0 | 8 | 6 |
| Team | 32 days | 23 points |
Without deducting holidays and leave, the team would have announced 36 points, 13 too many: more than half of its real capacity for this iteration.
Preparing PI planning
- Freeze assignments to the train for the PI: who, at what rate, on which iterations.
- Collect known leave, especially for PIs that cover summer or the end-of-year holidays.
- Calculate capacity per team and per iteration, in days and points.
- Keep a buffer: stretch objectives and the IP iteration absorb the unexpected; do not plan 100% of capacity as committed objectives.
Tracking the PI: from plan to actuals
During the PI, feature progress is tracked in the team's tool (Jira, Azure DevOps). Time consumed is tracked in time entries: days spent per person and per week, against planned capacity. This reconciliation answers management's and the customer's questions: how many days did this PI cost, was the team available as planned, what is left of the budget?
Capalane calculates capacity per PI with public holidays (France and Tunisia), leave and allocation rates, collects each week's time and produces reports by PI, by project and by person, in days and amounts.
SAFe and Scaled Agile Framework are trademarks of Scaled Agile, Inc. This guide is independent.
Frequently asked questions
How long is a SAFe PI?
Usually 8 to 12 weeks, most often 10: four two-week development iterations followed by an Innovation and Planning (IP) iteration. The duration is set by the Agile Release Train and stays stable from one PI to the next.
What are normalized story points?
A starting convention proposed by SAFe for teams without history: 8 points per full-time developer or tester per two-week iteration, minus one point per day of leave or public holiday. It gives all teams of a train a common baseline; measured velocity replaces it afterwards.
Should the IP iteration count towards capacity?
Not for PI objectives: the Innovation and Planning iteration acts as a buffer and is used for innovation and preparing the next PI. Its time should still be tracked in days and budget, like the rest of the PI.
Points or days: which should we track for the budget?
Days. Points are for planning with the team; budget, billing and contractual capacity are tracked in days and money. Both views coexist on the same PI.
Track your projects and resources in one place
Capalane calculates capacity with public holidays and leave, collects time in a grid that types like Excel and produces reports by project, by PI and by person.
Discover Capalane