---
title: "PI Planning Training Preparation - A Complete Guide"
description: "Master PI planning training preparation with practical steps to align your teams, sharpen objectives."
url: "https://agile-training.co.uk/pi-planning-training-preparation/"
---

# PI Planning Training - Preparing Your Teams for Programme Increment Events

Programme Increment planning is a two-day, face-to-face event where every team in a SAFe Agile Release Train aligns on objectives for the next 8–12 weeks. Without structured PI planning training preparation, those two days quickly become expensive confusion. Teams that arrive without context, clear roles, or practised facilitation skills routinely produce plans that collapse within the first sprint.

## Why Training Before the Event Matters

PI planning is not a meeting you can wing. Each team must understand their capacity, their dependencies on other teams, and the programme-level features they are committing to deliver. Organisations that invest even one focused training day beforehand report fewer mid-increment scope changes and cleaner dependency boards.

The cost of under-preparation is concrete. A single Agile Release Train with ten teams can consume 200+ person-hours across a two-day event. Spending those hours reworking fundamental concepts that should have been covered weeks earlier is avoidable waste.

## Core Skills to Build Before PI Planning

### Reading and Responding to the Programme Board

The programme board is the visual centrepiece of PI planning. Teams plot their planned features, mark inter-team dependencies, and flag risks. Practitioners who have never seen one before the event will spend the first morning just understanding the format rather than contributing to it.

Run at least one mock programme board session two to three weeks before the event. Use fictional features and ask each team to identify two or three dependencies. That single exercise reduces on-the-day confusion dramatically.

### Writing Meaningful Team PI Objectives

Team PI objectives are the short, business-value-scored commitments each team makes for the increment. Vague objectives such as "improve performance" are nearly impossible to score and impossible to track. Training should focus on writing objectives that are outcome-based, time-boxed to the increment, and verifiable by a product owner.

A useful format: state the capability delivered, the user or system affected, and the sprint in which it completes. Teams that practise this format in a workshop setting before PI planning arrive ready to draft their objectives in under 30 minutes.

### Capacity and Load Estimation

Over-commitment is the most common PI planning failure mode. Teams often forget to subtract public holidays, support rotations, and planned leave before calculating their available capacity. A short training exercise where each team calculates their actual sprint hours across all five sprints, including an innovation and planning sprint, corrects this habit before it becomes a problem.

Capacity worksheets do not need to be complex. A simple spreadsheet with team member names, available days per sprint, and a standard velocity figure is sufficient.

## Structuring Your Pre-PI Training Programme

### Four to Six Weeks Before

Focus on foundations. Run a half-day SAFe overview for anyone joining the train for the first time. Cover the roles: Release Train Engineer, Product Management, System Architect, and Business Owners. Clarify that PI planning is a planning event, not a status meeting.

Assign pre-reading: the relevant SAFe articles on PI objectives and the programme board. Keep this light, two to three short reads maximum, so it actually gets done.

### Two to Three Weeks Before

Conduct a full mock PI planning session. This does not need to replicate every ceremony, but it should include a simulated Business Context presentation, a mock Architecture Vision, team breakout sessions, and a draft programme board review. Recording common sticking points from this mock gives your Release Train Engineer a focused coaching agenda for the final week.

This is also the right time to confirm logistics: room layout, digital tools such as Miro or Jungles if the event is hybrid, and any travel arrangements for distributed team members.

### One Week Before

Share the finalised programme backlog with all teams. Product Management should have ranked features clearly, with acceptance criteria visible. Teams cannot walk into day one ready to plan if they are encountering features for the first time.

Hold a 60-minute coach clinics session for Scrum Masters and Product Owners. Address outstanding questions about how to handle cross-team dependencies and what to do when capacity clearly cannot absorb the planned features.

## Running the Actual PI Planning Event

### Day One

Day one opens with Business Context, delivered by senior leadership, followed by the Product Management vision and the Architecture Vision. These briefings should total no more than three hours. Teams then move into breakout sessions to draft their iteration plans and begin identifying risks and dependencies.

The most valuable facilitation move on day one is a mid-afternoon dependency review. Teams walk the programme board together and physically draw dependency lines before the day ends. Problems caught here cost minutes to resolve. The same problems found on day two cost hours.

### Day Two

Day two centres on finalising team PI objectives, completing the programme board, and running the Management Review and Problem-Solving session. This is where over-committed teams renegotiate scope with Business Owners present. It is also where the Risk Roam happens: each identified risk is marked as Resolved, Owned, Accepted, or Mitigated.

The event closes with a confidence vote. Each person holds up one to five fingers to signal their confidence in the collective plan. A fist, meaning zero confidence, triggers immediate discussion. A healthy train typically reaches an average vote of 3.5 or above before dispersing.

## Common Mistakes That Training Prevents

Arriving without a prioritised feature list is the single most disruptive error Product Management can make. When features are not ranked, teams cannot make rational trade-off decisions during breakout sessions.

A second common mistake is treating the programme board as a decoration rather than a working tool. Teams that do not update it in real time during breakouts produce a board that looks complete but does not reflect actual commitments. Daily programme board reviews during the increment keep this honest.

Finally, neglecting Business Owner attendance is a structural failure. Business Owners must be present and empowered to make scope decisions. Training should explicitly brief Business Owners on their role, particularly in the Management Review session, so they arrive prepared rather than passive.

## Keeping Momentum After PI Planning

PI planning training preparation does not end when the event does. The first sprint review after PI planning is an early signal of whether the planning quality was adequate. If teams are already descending from their PI objectives by sprint two, the root cause is almost always either over-commitment during planning or unclear acceptance criteria on features.

Schedule a brief retrospective on the PI planning event itself within the first two weeks of the increment. Capture what slowed teams down, which facilitation steps added the most value, and what briefing materials were missing. That feedback loop is what sharpens the next PI planning cycle from good to genuinely effective.

## Frequently Asked Questions

### What Is PI Planning in Scrum?

**PI planning is not a native Scrum ceremony but a SAFe (Scaled Agile Framework) event that sits above the team level.** It is a two-day session where all teams on an Agile Release Train align on objectives, dependencies, and delivery commitments for the next Programme Increment, typically 8–12 weeks covering five sprints. Scrum teams participate by drafting iteration plans and PI objectives within their standard sprint cadence structure.

### What Are Some Ways to Improve My Planning Skills?

**Practice estimating capacity accurately by tracking actual available hours across a sprint, subtracting leave and support duties before committing.** Run mock planning sessions using fictional features to build comfort with dependency mapping and objective writing. Reviewing completed PI plans against actual outcomes after each increment is one of the fastest ways to sharpen judgment about what realistic commitments look like.

### What Is a PI Meeting?

**A PI meeting refers to Programme Increment planning, the two-day event in SAFe where every team in an Agile Release Train comes together to plan the upcoming increment.** It includes Business Context and vision briefings from leadership, team breakout sessions to build iteration plans, a programme board to visualise dependencies, and a final confidence vote on the collective plan. It is the primary alignment mechanism for large-scale agile delivery.

### How to Prepare for a Sprint Planning Meeting?

**Ensure the product backlog is refined and prioritised before the meeting, with acceptance criteria written for the top items.** The development team should know their velocity and available capacity for the sprint, accounting for any holidays or reduced availability. Reviewing the PI objectives relevant to the upcoming sprint helps the team connect their sprint goal to the broader increment commitment.

### What Activities Are Done in Sprint Planning?

**Sprint planning typically covers three activities: agreeing on a sprint goal, selecting backlog items the team is confident they can complete, and breaking selected items into tasks with rough hour estimates.** The product owner clarifies acceptance criteria for any item the team is uncertain about. In a SAFe context, the team also checks that their sprint plan supports their PI objectives and flags any emerging dependency issues with other teams.
