What is an IP Iteration anti-pattern?

The correct choice highlights the practice of planning work for the Innovation and Planning (IP) Iteration during Program Increment (PI) Planning. This approach is aligned with the SAFe framework's emphasis on structured planning, where teams focus on maximizing value delivery and aligning on future work during the PI Planning sessions.

Planning work for the IP Iteration at this stage helps ensure that teams allocate dedicated time for innovation, exploration, and reflection, rather than pushing these activities aside. The IP Iteration serves as a critical period for teams to address various needs, such as technical improvements or skills development, and by specifying work for this phase during PI Planning, teams can better manage their backlogs and prioritize activities that enhance the overall architecture and quality of the product.

The other options, while relevant to the context of iterations and innovation, do not directly describe the anti-pattern within the context of the IP Iteration. Identifying opportunities for innovation spikes and infrastructure improvements can be beneficial but doesn't explicitly convey the concept of planning work during the PI. Allowing for cadence-based planning is important but is a general practice that applies to the entirety of the cadence within SAFe, rather than focusing specifically on the IP Iteration's planning aspect. Thus, they do not directly address the