Facilitating PI Planning: How to ensure a successful session?

PI Planning is the key moment within SAFe (Scaled Agile Framework) when all teams within an Agile Release Train (ART) come together to establish the goals and planning for the upcoming 8-12 weeks to set. As a facilitator – often a Release Train Engineer (RTE) or experienced Scrum Master – you have the task of leading this session effectively. This means: setting clear goals, enabling teams to collaborate effectively, and ensuring all dependencies are discussed.

A poorly facilitated PI Planning can lead to vague agreements, misunderstandings, and delays in execution. A well-facilitated session, on the other hand, ensures clear goals, realistic plans, and strong commitment from all teams and stakeholders.

‍

The Core of PI Planning

During PI Planning, it is determined what value the ART will deliver in the upcoming Program Increment. The planning lasts two days and revolves around three main questions:

1. What are the strategic goals and priorities?
   Product Management and Business Owners present the product vision and roadmap. This helps teams understand the main focus areas and where the most value lies.
2. How can teams coordinate their work and manage dependencies?
   Teams work individually and collaboratively on their plans, identify dependencies, and resolve bottlenecks. This is done using a Program Board, which visually displays who is dependent on whom.
3. How do we ensure a shared commitment to the PI goals?
   At the end of the planning session, teams vote on their confidence in the feasibility of the plans. This is done with a Confidence Vote: if the majority is confident, the PI begins. If not, then plans are adjusted.

‍

The role of the facilitator

A successful PI Planning hinges on effective facilitation. As a facilitator, you ensure that:

• The right people are present and know what is expected of them.
• The agenda is clear and there is sufficient time for both team planning and collective alignment.
• Teams are not only focused on their own work, but also consider dependencies.
• Roadblocks and risks are identified early and are addressed.

This requires a balance between structure and flexibility. There must be enough room to adjust plans based on new insights, without the session devolving into endless discussions.

‍

Facilitating a successful PI Planning: step by step

Preparation

A good PI Planning starts well in advance. Product Management needs to have the backlog organized, teams need to understand their dependencies, and the necessary tools must be ready. For remote sessions it's especially important to test beforehand whether all digital tools (such as Miro, Jira or SAFe Collaborate) are working correctly.

Tip: Ensure all teams have an overview beforehand of their planned features and technical challenges. This saves a lot of time during the session.

Day 1: Context and initial planning

The first day begins with establishing the business context. Product Management and Business Owners share the strategy and vision, after which the Program Backlog is presented. This helps teams understand priorities and better assess the impact of their work.

After this introduction, teams start working on their own planning. During the first breakout session teams distribute work from the backlog, estimate complexity, and identify dependencies with other teams. They then present their preliminary plan and receive feedback.

A common problem is that teams delve too deeply into details and consequently fall behind schedule. This presents an important task for the facilitator: ensure that teams remain focused on the bigger picture and don't get bogged down in technical details that can be discussed later.

Day 2: Fine-tuning and commitment

The second day focuses on refinement and alignment. Teams process the feedback from day 1 and make their plans more concrete. Dependencies are reviewed and prioritized again, so that any potential risks can be addressed in a timely manner.

A crucial phase is the ROAM session, where teams collectively discuss and categorize risks:

• Resolved (resolved)
• Owned (a team takes responsibility)
• Accepted (risk is accepted)
• Mitigated (measures are taken to reduce the risk)

At the end of the day, teams present their final plans and vote in a Confidence Vote on the feasibility of the PI. If confidence is insufficient, plans are adjusted until there is sufficient buy-in.

Common mistakes in PI Planning

1. Insufficient preparation
   If the backlog is not well prepared, teams waste a lot of time on ambiguities and discussions about priorities. Ensure everything is clear beforehand.
2. Too much focus on individual teams, too little on collaboration
   PI Planning is not just a team session, but primarily a collaboration between teams. Make dependencies explicit and encourage interaction.
3. Stakeholders are too passive
   Business Owners and other stakeholders must be actively involved and provide timely input, not just be present as spectators.
4. No clear action items after the session
   The success of PI Planning depends on strong follow-up. Ensure that all agreements and dependencies are immediately documented and followed up on.