Innovation and Planning (IP) Iteration
In SAFe, a time-boxed sprint dedicated to exploration, innovation, and improvement work.
Key Points
- Scheduled as a dedicated iteration to support learning, experimentation, and continuous improvement.
- Used for activities like spikes, prototyping, hackathons, refactoring, automation, and addressing technical debt or defects.
- Provides a capacity buffer that helps teams meet PI objectives without over-committing.
- Supports readiness for the next PI through planning, training, and Inspect and Adapt activities.
Example
A release train plans an IP iteration after several development sprints. The team prototypes a new API, automates parts of the CI/CD pipeline, fixes critical defects, documents coding standards, and finalizes inputs for the upcoming PI planning event.
PMP Example Question
During a Program Increment, the team needs dedicated time to explore a new cloud service, reduce technical debt, and get ready for the next PI planning without risking current commitments. What should the Release Train Engineer schedule?
- Innovation and Planning (IP) Iteration
- Hardening sprint
- Daily Scrum
- Backlog grooming workshop
Correct Answer: A - The IP iteration reserved for exploration, innovation, improvement, and planning in SAFe
Explanation: The IP iteration is explicitly set aside for experimentation, improvement work, and preparation for the next PI; the other options do not provide this focused, time-boxed capacity.