Innovation and Planning (IP) Iteration
This right here is one of the most exciting things about SAFe!
The Innovation and Planning (IP) Iteration is a unique, dedicated, 2-week Iteration that occurs every PI (a cycle of 8-12 weeks). It provides an estimating buffer for meeting PI Objectives and dedicated time for innovation, continuing education, PI Planning, and Inspect and Adapt (I&A) events.
All of Agile recommends innovation, experiments, skills development and continuous learning along with so many other great concepts but you would find that a lot of these happen in principle but not in practice. SAFe is the only framework that has taken the initiative to practice what it preaches by actually creating this dedicated 2-week period every PI to ensure that these great concepts are brought to fruition, along with their daily applications. I have often found non-SAFe teams struggling with time to innovate, learn, grow, because they are too busy completing current tasks with no bandwidth to prepare for the future, or God forbid, their personal development.
Atlassian is one of the many organizations that is benefitting from this practical application of Business Agility, through its use of the concept it calls “ShipIt Days.” How this works is that every 90 days, for 24 hours, Atlassian employees can work on whatever they want (it doesn’t need to be job-related). The teams self-organize and present a prototype of something that can be any product of their imagination, the format they use is called “Hackathons.” Many of the great features you see from Atlassian products such as: Jira, Jira Align, Jira Advanced Roadmap, Confluence and at a more granular level, the issue type known as a “Spike” evolved from this initiative.
Here are some of the benefits of this great initiative from SAFe: better predictability and flow, increased employee engagement and reduced burn-out, greater agility and resilience, increased competitive advantage. Find a more detailed explanation below:
1. Dedicated Time for Innovation:
The Innovation and Planning Iteration provides a dedicated time window for teams to focus on innovation and creative exploration. In the fast-paced world of solution development, where constant delivery is essential, having a designated period for brainstorming, experimentation, and idea generation is invaluable. This intentional focus on innovation ensures that teams do not get bogged down solely by the day-to-day demands of product delivery but also have the space to explore novel ideas and solutions.
2. Strategic Planning and Roadmap Development:
During the IP Iteration, teams engage in strategic planning activities to align their objectives with broader organizational goals. This involves reviewing and refining the Product Roadmap, setting priorities, and establishing a clear vision for the upcoming Planning Intervals (PIs). This strategic planning not only enhances the alignment of teams but also ensures that development efforts are in sync with the overall business strategy.
3. Capacity for Refinement and Learning:
The Innovation and Planning Iteration offers a unique opportunity for teams to reflect on their past performance, inspect and adapt their processes, and identify areas for improvement. This capacity for refinement and learning contributes to a culture of continuous improvement, where teams are empowered to evolve and optimize their practices based on feedback and insights gained from previous iterations.
4. ART Backlog Grooming and Preparation:
An essential aspect of the IP Iteration is the ART Backlog Refinement and preparation. Teams use this time to refine and prioritize the ART Backlog, ensuring that upcoming work is well-defined and ready for execution in the subsequent PI. This proactive approach to ART Backlog refinement contributes to more efficient planning and execution in the following Iterations.
5. Enhanced Cross-Team Collaboration:
The IP Iteration encourages cross-team collaboration and communication. As teams come together to plan and strategize, they gain a deeper understanding of each other’s priorities, dependencies, and challenges. This enhanced collaboration fosters a sense of unity and shared purpose, breaking down silos and promoting a more cohesive and integrated approach to development.
6. Reduced Technical Debt:
In the rush to meet tight deadlines, technical debt can accumulate, leading to long-term challenges in product development. The IP Iteration provides teams with the opportunity to address and mitigate technical debt. By dedicating time to refactor code, improve system architecture, and address technical challenges, teams can ensure the long-term sustainability and maintainability of their products. This can also be used for early fixes for non-software products.
7. Alignment with Market Trends:
Innovation is not just about internal exploration; it also involves staying attuned to external market trends. The IP Iteration allows teams to assess and incorporate emerging technologies, industry trends, and customer feedback into their development strategies. This alignment with market trends ensures that products remain competitive and relevant in a rapidly changing business environment.
In summary, the Innovation and Planning Iteration in SAFe, is not just a pause in the development cycle; it’s a strategic and transformative interval that empowers teams to unleash their creativity, align with organizational goals, and foster a culture of continuous improvement. By recognizing the value of dedicated time for innovation and planning, organizations can elevate their development practices, stay ahead of the competition, and navigate the complexities of the ever-evolving product landscape with agility and foresight.
Questions and comments are welcome.