What’s inside this PI Planning Meeting Template
Program Increment (PI) Planning is a face-to-face, cadence-based event that acts as the heartbeat of the Agile Release Train (ART), uniting all of the ART’s teams around a common objective and vision.
This 2-day agenda was curated by the Scaled AGILE team.
Day 1 Agenda
1 Business context
A firm owner or senior executive discusses the current state of the company, the Portfolio Vision, and how well existing solutions are meeting current consumer needs.
2 Product/solution vision
Product Management gives the current vision as well as any modifications since the previous PI planning event and any approaching Milestones.
3 Architecture vision and development practices
The vision for the architecture is presented by System Architect/Engineering. A senior development manager may also implement Agile-friendly modifications to development techniques
4 Planning context and lunch
The RTE outlines the planning process as well as the anticipated outcomes.
5 Team breakouts #1
Teams assess their capacity for each Iteration and identify the backlog items they will most likely require to materialise the features in the breakout.
6 Draft plan review
Teams submit critical planning outputs such as capacity and load, draught PI objectives, potential risks, and dependencies during the tightly timeboxed draught plan review.
7 Management review and problem-solving
The draught plans are likely to have issues. Management may negotiate scope changes and other issues during the problem-solving meeting by agreeing to various planning adjustments.
Day 2 Agenda
1 Planning adjustments
The following day, management will present any changes to the planning scope, people, and resources.
2 Team breakouts #2
Teams continue to plan based on the previous day’s programme, making revisions as necessary. They formalise the PI’s objectives, and the Business Owners attach business value to them.
3 Final plan review and lunch
All teams submit their plans to the group during this session. At the end of each team’s time slot, the team declares its risks and barriers, and the RTE records them for further use in the ROAMing process.
4 Program risks
During the planning process, teams identified programme risks and impediments that could jeopardise their capacity to achieve their goals. Risks are categorized into: resolved, owned, accepted, and mitigated.
5 Confidence vote
Teams vote on their confidence in attaining their team PI targets after programme risks have been handled.
6 Plan rework
Teams revise their plans as needed until they achieve a high level of confidence. This is one time when commitment and alignment take precedence over sticking to a schedule.
7 Planning retrospective and moving forward
Finally, the RTE facilitates a brief retrospective for the PI planning event in order to document what went well, what didn’t, and what can be improved for the next time.