Program increment (PI)
A Program Increment is SAFe's timebox for an Agile Release Train — typically 8-12 weeks, usually 5 iterations of 2 weeks each. The PI is the planning, execution, and inspection unit above the iteration: the ART commits to PI Objectives at PI Planning, demos progress at the System Demo each iteration, and inspects at the end.
The PI cadence is deliberately longer than an iteration but shorter than a quarter: long enough to deliver substantive end-to-end value (a feature with real architectural depth), short enough that re-planning happens before market conditions invalidate the plan. The structure typically includes 4 development iterations plus 1 'IP' (Innovation and Planning) iteration at the end — used for hardening, exploratory spikes, training, and the next PI Planning event. Teams new to SAFe often try to skip the IP iteration to 'maximise output'; this almost always backfires because the cadence loses its breathing room.
Related terms
- Agile release train (ART)
An Agile Release Train is a long-lived team-of-teams in SAFe — typically 50-125 people across 5-12 Agile teams — that plans, commits, and releases together on a fixed cadence called a Program Increment (PI).
- PI planning
PI Planning is the 1-2 day event at the start of each Program Increment where the entire Agile Release Train — all teams, Product Management, Business Owners, System Architect — assembles to plan the upcoming PI.
- Inspect & adapt workshop
Inspect & Adapt is the SAFe event at the end of each Program Increment in which the ART reviews quantitative results (PI Objectives achieved, predictability measure, business value scoring), demos the integrated solution, and runs a structured problem-solving workshop on the top systemic improvements to commit to in the next PI.