The IP iteration is not spare capacity
Every PI contains an Innovation and Planning (IP) iteration. It is an estimating buffer for meeting PI Objectives, and dedicated time for innovation, continuing education, PI Planning itself, and the Inspect and Adapt event.
Why it is like this
A cadence with no slack cannot absorb variability, and a train with no protected time for learning stops improving within a couple of PIs. Naming the iteration is what stops both being the first thing cut.
Not to be confused with
Slack to be filled with features, or a catch-up sprint for work that overran. Planning features into the IP iteration removes the buffer that made the PI Objectives credible — and then the overrun has nowhere to go.
In practice
A train that routinely uses IP to finish committed work has told you its commitments were not forecasts. That is the signal worth reading, not the missed objective.
Source: SAFe Glossary (Scaled Agile, Inc.) — Innovation and Planning Iteration. 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.
Say it back Check yourself
Name the four things the Innovation and Planning iteration is for.
Answer out loud or in writing first, then open the points below.
The points a good answer makes
- An estimating buffer for meeting PI Objectives
- Dedicated time for innovation
- Continuing education
- PI Planning and the Inspect and Adapt event
If a team can only name the buffer, the innovation and education halves are almost certainly already being spent on delivery.