The Solution Train and Agile Release Trains follow the same PI cadence Experience has shown, however, that a PI duration between 8 and 12 weeks works best, with a bias toward shorter durations.Ī Solution Train and its associated Agile Release Trains use the same PI cadence, as shown in Figure 1. This pattern is suggestive but arbitrary, and there is no fixed rule for how many iterations are in a PI. SAFe divides the development timeline into a series of iterations within a PI. The Big Picture illustrates how a PI is initiated by a PI Planning event and is then followed by four execution iterations, concluding with one IP iteration. Assure consistent, ART wide retrospectivesĭue to its scope, the PI provides an appropriate timebox for Portfolio Level considerations and ‘roadmapping.’ Details.Summarize newsworthy value for feedback.Each PI applies cadence and synchronization to:
#Spike meaning in sprint full
It’s a fixed timebox for planning, building, and validating a full system increment, demonstrating value, and getting fast feedback. The most common pattern for a PI is four development Iterations, followed by one Innovation and Planning (IP) Iteration.Ī PI is to an Agile Release Train (ART) (or Solution Train), as an Iteration is to the Agile Team. A Program Increment (PI) is a timebox during which an Agile Release Train (ART) delivers incremental value in the form of working, tested software and systems.
0 kommentar(er)
