The IP iteration (Innovation & Planning Iteration) is a central element in the Scaled Agile Framework (SAFe). It takes place at the end of a Program Increment (PI) and serves as a buffer, innovation space, and planning time. While regular iterations focus on delivering features and stories, the IP iteration deliberately creates space for innovation, training, exploration, and preparation.
Practical relevance
The following activities typically take place in the IP iteration:
• Innovation & hackathons: Teams work on new ideas, prototypes, or technical improvements.
• Education & learning: Time for training, certifications, or skill building.
• PI Planning: Preparation and implementation of the next program increment.
• Inspect & Adapt: Joint review of the past PI and derivation of improvements.
The IP iteration is therefore more than just a "break" – it is a structured framework for sustainable development.
Typical Misconceptions & Criticism
❌ "Vacation week": Some organizations misunderstand the IP iteration as free time without a clear focus. In reality, it is about targeted investment in innovation, learning, and improvement.
❌ "A luxury we can't afford": Critics argue that time should be invested in features instead. Paradoxically, omitting the IP iteration leads to slower progress in the long term, as technical debt and a lack of innovation slow organizations down.
❌ "Only for SAFe": The principles of IP iteration—space for innovation and learning—are valuable regardless of the framework.
Relevance for organizations
• Promoting innovation: Freedom creates prototypes, new ideas, or process improvements that would otherwise be lost in day-to-day business.
• Ensuring quality: Teams can reduce technical debt or improve architectures.
• Continuous learning: Employees expand their skills and competencies.
• Sustainable planning: Integrating PI Planning and I&A aligns the organization.
Use outside of SAFe
Even organizations without SAFe can benefit from the IP iteration mindset, e.g., through:
• Innovation Days/Hack Weeks: Regular opportunities for experimentation.
• Learning sprints: Iterations specifically used for further training.
• Quarterly planning days: Periods for alignment, retrospectives, and strategy workshops.
Pragmatic example: A medium-sized company without SAFe established an "Innovation Week" every 10 weeks. Result: Numerous process improvements and two new product ideas that were directly incorporated into the roadmap.
Role of experienced catalysts
The quality of an IP iteration depends heavily on its design and moderation. Without a clear framework, it can easily degenerate into an "idle week." External impetus—for example, from experienced RTEs, agile coaches, or consulting firms—can help make the iteration effective:
• Impulses for innovative formats (e.g., design thinking, hackathons).
• Facilitation of large groups (e.g., PI Planning, I&A).
• Transfer of best practices from other organizations.
This demonstrates the value of partners with experience in designing such iterations, which both provide structure and promote creativity.
CALADE perspective
At CALADE, we see IP iteration as a key lever for innovation and sustainability. In our projects, we design these iterations to provide space for creativity, learning, and improvement—while ensuring the necessary alignment. To do this, we combine proven elements from SAFe with customized formats such as hackathons, design thinking sessions, and strategy sprints. This makes IP iteration a real driver of progress, rather than a compulsory exercise.
Related terms
• Program Increment (PI)
• Inspect & Adapt Workshop
• PI Planning
• Design Thinking
• Technical Debt