#Lion babe begin physical release full

ItвЂ™s equally important to ensure that there is a clear vision and context and that the right stakeholders can participate. Agile teams вЂ“ Do we have Agile teams? Are there dedicated team members and an identified Scrum Master and Product Owner for each team?.Business alignment вЂ“ Is there reasonable agreement on priorities among the Business Owners?.Planning scope and context вЂ“ Is the scope (product, system, technology domain) of the planning process understood? Do we know which teams need to plan together?.To address this in advance, however, event organizers must consider the following: Organizational ReadinessД«efore PI planning, there must beВ strategy alignment among participants, stakeholders, and Business Owners.

#Lion babe begin physical release full

(The full checklist is provided in the SAFe PI Planning Toolkit, available to SPCs).

Logistics readiness вЂ“ Considerations for running a successful eventД«elow are highlights of the ART Readiness Checklist.

Content readiness вЂ“ Management and development preparedness.

Organizational readiness вЂ“ Strategic alignment and teams and trains setup.

The active participation of Business Owners in this event provides an important Guardrail on budgetary spend.ДЇor the event to be successful, preparation is required in three major areas: It is facilitated by the RTE and event attendees include Business Owners, Product Management, Agile Teams, System and Solution Architects/Engineering, the System Team, and other stakeholders, all of whom must be notified in advance to be well prepared.

PI planning is a significant event that requires preparation, coordination, and communication.

Program board вЂ“ Highlighting the new feature delivery dates, feature dependencies among teams and relevant Milestones.

Committed PI objectives вЂ“ A set of SMART objectives that are created by each team with the business value assigned by the Business Owners.

Business context (see вЂcontent readinessвЂ™ below)ДЄ successful PI planning event delivers two primary outputs:.

Matching demand to capacity and eliminating excess Work in Process (WIP).

Providing the opportunity for вЂjust the right amountвЂ™ of architectureВ and Lean User Experience (UX) guidance.

Identifying dependencies and fostering cross-team and cross-ART collaboration.

Aligning development to business goals with the business context, vision, and Team and Program PI objectives.

Building the social network the ART depends upon.

Establishing face-to-face communication across all team members and stakeholders.

PI planning delivers many business benefits, including: PI Planning takes place over two days, although this is often extended to accommodate planning across multiple time zones. Holding the event during the IP iteration avoids affecting the scheduling, or capacity of other iterations in the PI.

Facilitated by the Release Train Engineer (RTE), this event includes all members of the ART and occurs within the Innovation and Planning (IP) Iteration. PI Planning has a standard agenda that includes a presentation of business context and vision, followed by team planning breakouts-where the teams create their Iteration plans and objectives for the upcoming Program Increment (PI). Remote teams are planning at the same time using video conferencing. The advanced topic article, Distributed PI Planning with SAFe, provides additional guidance and considerations for successfully managing these scenarios. Indeed many ARTs have been successful in creating a hybrid situation where several teams join remotely, as shown below in Figure 1. While physical face to face planning has its benefits, the unwritten SAFe вЂruleвЂ™ is вЂњthe people who do the work plan the work.вЂќ When physical presence is not possible, real time, concurrent, virtual, face to face planning has now proven to be effective. It may not always be practical for the entire Agile Release Train (ART) to collocate however, and in our current times COVID-19 has created a situation where this isnвЂ™t an option. They have clearly shown real financial ROI, not to mention the intangibles that occur when the team of Agile teams creates a social construct that is personally and collectively rewarding. Where possible this involves physical collocation, and these large scale PI planning events now take place within many enterprises around the world. The Agile Manifesto states, вЂњThe most efficient and effective method of conveying information to and within a development team is a face-to-face conversation.вЂќ SAFe takes this to the next level with PI planning.