SAFe - P.I. Planning [Day 1]

A Business Owner or senior executive describes the current state of the business, shares the Portfolio Vision, and presents a perspective on how effectively existing solutions are addressing current customer needs.

Product Management presents the current vision (typically represented by the next top 10 upcoming features) and highlights any changes from the previous PI planning event, as well as any forthcoming Milestones

System Architect/Engineering presents the architecture vision. Also, a senior development manager may introduce Agile-supportive changes to development practices, such as test automation, DevOps, Continuous Integration, and Continuous Deployment, which are being advanced in the upcoming PI.

The RTE presents the planning process and expected outcomes.

In the breakout, teams estimate their capacity for each Iteration and identify the backlog items they will likely need to realize the features. Each team creates their draft plans, visible to all, iteration by iteration.

During the tightly timeboxed draft plan review, teams present key planning outputs, which include capacity and load, draft PI objectives, potential risks, and dependencies. Business Owners, Product Management, and other teams and stakeholders review and provide input.

It’s likely that the draft plans present challenges such as scope, people and resource constraints, and dependencies. During the problem-solving meeting, management may negotiate scope changes and resolve other problems by agreeing to various planning adjustments. The RTE facilitates and keeps the primary stakeholders together for as long as necessary to make the decisions needed to reach achievable objectives.