MENU
Three teams in the Agile Release Train are working on the same Feature. Team A is a complicated subsystem team, and Teams B and C are stream-aligned teams. During PI Planning, Teams B and C committed to delivering their part of the Feature by the end of Iteration five and plan to integrate with each other along with Team A's piece in the first week of the IP Iteration. Why is this an anti-pattern?
In SAFe, the Innovation and Planning (IP) Iteration is reserved for activities such as innovation, planning, and preparation for the next Program Increment (PI), as well as for holding the Inspect and Adapt (I&A) event. It is not intended for completing work that should have been finished during regular iterations. Planning work for the IP Iteration can lead to a lack of focus on essential planning and innovation activities and may indicate poor planning and risk management practices. Therefore, relying on the IP Iteration to complete Feature work is considered an anti-pattern.
SAFe Scrum Master Reference
SAFe 5.0 framework: guidelines on the purpose and use of the IP Iteration
SAFe Advanced Scrum Master learning materials