Planning Interval, formerly Program Increment
A Planning Interval (PI) is a cadence-based timebox in which Agile Release Trains deliver continuous value in alignment with PI Objectives. It was called a *Program Increment* until SAFe 6.0, which renamed it while keeping the "PI" acronym.
Why it is like this
"Increment" named an output, which encouraged treating the PI as a fixed scope container; "Interval" names a duration you plan and steer within. The acronym stayed so that a decade of material, tooling and job titles did not all break at once.
Not to be confused with
A release, or a big Sprint. Nothing has to ship at a PI boundary — release is decoupled from the cadence — and the PI is a planning and steering rhythm rather than a scope commitment.
In practice
The retained acronym is a trap in conversation: two people can say "PI" for a year and mean subtly different things, one of them a container of scope.
Source: SAFe Glossary (Scaled Agile, Inc.) — Planning Interval (PI). Read on .
SAFe® and Scaled Agile Framework® are registered trade marks of Scaled Agile, Inc. ytyk.org is not affiliated with, endorsed by or licensed by Scaled Agile, Inc. These cards are independent commentary written in our own words; no SAFe text, graphic or Big Picture is reproduced here.
Predict Check yourself
A colleague says "we committed that scope for the Program Increment". What is out of date, and what is the subtler problem?
Show the answer
"Program Increment" was renamed Planning Interval in SAFe 6.0 — and "committed that scope" treats the PI as a scope container rather than a planning and steering interval.
The rename was made precisely to stop the second half of that sentence, which is why spotting only the vocabulary misses the point.