The RTE, representatives from each team (often the Scrum Master), and others (where appropriate) meet to review their progress toward milestones and PI objectives, and dependencies among the teams. The SoS helps coordinate the dependencies of the ARTs and provides visibility into progress and impediments. The Release Train Engineer (RTE) typically facilitates a weekly (or more frequently, as needed) Scrum of Scrums (SoS) event. Of course, Agile teams continuously integrate their work and demo it during the Iteration Review and System Demo (or Solution Demo for Solution Trains) Scrum of Scrums One outcome of the PI planning is a set of PI Objectives, detailing what the ART should have ready to demonstrate at the end of the PI. It also helps people on the train, especially Business Owners, to manage their other commitments to ensure they can be present for these critical events.ĭuring PI planning, the teams estimate what will be delivered and highlight their dependencies with other Agile teams and trains. By scheduling PI planning events in advance, the Enterprise can lower the cost of travel and logistics. Since PI planning occurs on a fixed cadence, the entire calendar year of events can be scheduled well in advance. PI PlanningĮach PI begins with a PI planning event. ART eventsĮach event is described in the next sections. When it comes to PI execution for a single ART, a sequence of events creates a closed-loop system to keep the train on the tracks, as illustrated in Figure 2. Still, others will have multiple, independent release cycles for the solution’s various components. ![]() Some ARTs may need to release more or less frequently than the PI cadence. However, in some situations, the PI and release cadences are the same, particularly in large supply chains (see the supply chains discussion in Enterprise Solution Delivery). The planning cadence is often different from the release cadence. While trains determine the best product development rhythm, the business is enabled to deploy releases whenever it, or the market, requires. Releasing solutions, however, is a separate concern, which is covered in the Release on Demand article. Adjust – The Inspect and Adapt (I&A) is the adjustĬontinuous execution of PIs provides the rhythm for trains, and the assets they create to grow iteratively and incrementally.Plan – The PI Planning event is the plan step of the cycle.This PI (outer loop) PDCA learning cycle is represented in SAFe by the following ART events and activities: It combines the value developed by each Agile team into a meaningful Milestone to objectively measure the Solution under development. The PI represents the outer loop of the Shewhart PDCA cycle as shown at the top of Figure 1. ![]() 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |