In 30 seconds
- A fixed timebox for an Agile Release Train.
- Starts with PI Planning; ends with inspect and adapt.
- Often four development iterations plus one innovation and planning iteration.
Structure
A typical PI has several development iterations (often four two-week sprints), followed by an innovation and planning (IP) iteration. Recent SAFe versions call it a Planning Interval while keeping the PI abbreviation.
Key events
- PI Planning at the start
- System demos throughout
- Inspect and adapt at the end
The IP iteration
The innovation and planning iteration gives buffer for unfinished work, time for hackathons and learning, and space to prepare the next PI Planning. It protects sustainable pace across the train.
Myth vs reality
Myth · A PI is a mini-waterfall.
Reality · Teams still deliver every iteration.
Myth · The IP iteration is spare capacity for features.
Reality · It's for innovation, learning and planning.
Myth · All work must wait for the next PI.
Reality · Changes can be absorbed within a PI when needed.
FAQ
Why 8 to 12 weeks?
Long enough for meaningful outcomes, short enough to adapt.
Is a PI the same as a release?
No; teams can release anytime during a PI.
What happens at inspect and adapt?
A demo, metrics review and problem-solving workshop.