Many companies tend to overlook the IP Iteration, but it is a crucial element for the proper functioning of your SAFe application. Treating it as just another regular iteration can lead to several issues.
The IP Iteration
As people learn in their SAFe training, a Program Increment (PI) consists of 5 two-week iterations in its most classic version, with the last one being the IP (Iteration Planning) iteration.
IP iteration
As you can see, the fifth iteration is not primarily meant for direct product work. However, it can serve this purpose if there are delays in achieving the PI objectives.
Here’s an example provided by SAFe for the work included in this particular iteration:
This iteration allows you to:
- Complete remaining work if necessary.
- Conduct the 2-day PI planning (and its preparation).
- Utilize the time for team training.
- Engage in innovation activities.
Neglecting to fill this iteration, as many companies do, can lead to over-pressurizing the teams. This loss of motivation can result in reduced productivity.
This iteration is essential for the overall balance of the teams and helps to avoid additional pressures due to deadline overruns. It also serves as a buffer to complete the initial PI objectives when they are not entirely finished. If teams fill this iteration with tasks, there is no buffer left, and unachieved objectives often lead to significant disappointment.
Conclusion
If your company doesn’t adhere to this essential fifth IP iteration for the smooth operation that SAFe aims to achieve, remind them that it’s an official part of the framework and carries many benefits. Also, emphasize the observed delays and the disappointment associated with unmet objectives (which is almost always the case when it’s not implemented).
Be the first to comment