Day 1
Business context
The senior executives discuss the company's current state, the Portfolio Vision, and how well existing solutions meet everyday consumer needs.
Product/solution vision
Product presents the current vision and any modifications since the previous PI planning event and any approaching Milestones.
Architecture vision and development practices
System Architect/Engineering presents the vision for the architecture.
Planning context and lunch
Outline the planning process as well as the anticipated outcomes.
Team breakouts #1
Teams assess their capacity for each Iteration and identify the backlog items they will most likely require to materialize the features in the breakout.
Draft plan review
Teams submit critical planning outputs such as capacity and load, draught PI objectives, potential risks, and dependencies while reviewing the tightly timeboxed draught plan.
Management review and problem-solving
The draught plans are likely to have issues. During the problem-solving meeting, management may negotiate scope changes and other matters by agreeing to various planning adjustments.
Day 2
Planning adjustments
The following day, management will present any changes to the planning scope, people, and resources.
Team breakouts #2
Teams continue to plan based on the previous day's programme, making revisions as necessary.
Final plan review
All teams submit their plans to the group during this session.
Program risks
During the planning process, teams identified programme risks and impediments that could jeopardize their capacity to achieve their goals.
Confidence vote
Teams vote on their confidence in attaining their team PI targets.
Plan rework
Teams revise their plans as needed until they achieve a high level of confidence.
Planning retrospective and moving forward
Finally, the RTE facilitates a brief retrospective for the PI planning event to document what went well, what didn't, and what can be improved next time.
Action items
What are the next steps?
.svg)
