How to run PI Planning and keep a record of every team's plan
PI Planning is the SAFe event where every team on an Agile Release Train plans the next Planning Interval together. It usually runs two days every 8–12 weeks. It should end with committed PI objectives, an ART planning board, risks sorted with ROAM and a confidence vote. With many teams planning at once, decide up front how each team's plan gets recorded.
What PI Planning is
In the Scaled Agile Framework (SAFe), PI Planning aligns all the teams on an Agile Release Train (ART) and their stakeholders around one plan. An ART is a long-lived team of Agile teams, generally 50 to 125 people.
SAFe describes it as typically a two-day event held every 8–12 weeks. Each Planning Interval (PI) begins with it, and the Release Train Engineer (RTE) leads it.
- Align development with business goals and context.
- Surface dependencies between teams and across ARTs.
- Match demand to capacity and cut excess work in process.
- Make decisions quickly, with the people who do the work in the room.
What it must produce
SAFe's facilitator guide lists committed objectives, the planning board and addressed risks as the outcomes. The confidence vote is how the ART makes its commitment at the end of day two.
| Output | What it is |
|---|---|
| PI objectives | Each team's business and technical goals for the PI, marked committed or uncommitted, rolled up into ART PI objectives |
| ART planning board | A visual of feature delivery dates, dependencies between teams and key milestones |
| ART PI risks | Remaining risks, each sorted as Resolved, Owned, Accepted or Mitigated (ROAM) |
| Confidence vote | Teams, Business Owners and ART leadership vote on their confidence in meeting the objectives, with a show of five fingers |
Who attends
- Every Agile team on the ART: Scrum Masters or Team Coaches, Product Owners, and Developers and Testers.
- Product Managers, who present the vision and feature priorities.
- System Architects, who present the architecture vision.
- Business Owners, who set business context and assign business value to objectives.
- The Release Train Engineer, who facilitates.
A typical two-day agenda
SAFe notes the agenda varies with each ART's context. This is the typical shape from its facilitator guide.
| When | What happens |
|---|---|
| Day 1 morning | Opening, then business context from a Business Owner, the product vision from Product Management and the architecture vision from System Architects |
| Day 1 afternoon | Team planning breakouts: estimate capacity, sequence stories, find dependencies, draft PI objectives and risks. Scrum Masters sync on dependencies each hour |
| Day 1 end | Draft plan review by each team, then a management review to resolve scope and constraint problems |
| Day 2 morning | Management shares its decisions, and teams adjust their plans in breakouts |
| Day 2 afternoon | Teams finalize objectives, Business Owners assign business value, and the planning board is brought up to date |
| Day 2 late afternoon | Final plan review, ROAM of remaining risks, the confidence vote and a short retrospective on the event |
Prepare three kinds of readiness
SAFe groups preparation into organizational readiness, content readiness and logistics, or facility, readiness. On content, it asks for prioritized features, a clear product and architecture vision, and established business context.
On top of that, we suggest three practical checks before day one:
- Book the right people for both days, including Business Owners.
- Have the vision and the top features ready to present.
- Set up and test rooms or video links, breakout spaces and a shared planning board.
Example: a committed and an uncommitted objective
This example is hypothetical. A payments team writes two PI objectives for the next PI.
Committed: "Customers can save a second card at checkout, released to all regions." The team has capacity and no open dependencies.
Uncommitted: "Add a wallet payment option, pending the security review from the platform team." It depends on another team, so the team marks it uncommitted and puts the dependency on the ART planning board.
Running it with remote teams
SAFe prefers having everyone physically together. Its guide says real-time, concurrent, virtual planning works when that isn't possible, with a shared digital board and clear audio and video for everyone.
Remote PI Planning usually means many parallel team breakouts. Name a note-taker in each one, so draft objectives, risks and dependencies come back to the whole ART intact.
After PI Planning
After the event, SAFe's guide has teams record their objectives and stories in their tooling and roll team objectives up into ART PI objectives. Product Management updates the roadmap.
At the end of the PI, the Inspect and Adapt event demonstrates and evaluates the solution, reviews measurements and runs a problem-solving workshop. It is easier to run when the original plan is easy to find.
Planning with Bridge
Host the plenary sessions on Bridge Business, which allows 200 participants and meetings up to 24 hours. Or capture them from Zoom, Google Meet or Microsoft Teams.
Each recorded session ends with a summary, decisions and action items, plus a speaker-labeled transcript. On Zoom, Bridge Agent can capture one breakout room, the room it is assigned to.
Add each PI's planning sessions to one space and label them. When Inspect and Adapt comes around, the commitments and the discussion behind them are in one place.
Sources & further reading
- Scaled Agile: SAFe PI Planning Facilitator’s Guide ↗
- Scaled Agile Framework: PI Planning ↗
- Scaled Agile Framework: PI Objectives ↗
- Scaled Agile Framework: Planning Interval ↗
- Scaled Agile Framework: Agile Release Train ↗
- Scaled Agile Framework: Inspect and Adapt ↗
- Scaled Agile Framework: Glossary ↗
- Bridge pricing ↗
- Bridge help center: Notetaking ↗
- Bridge help center: Capture a virtual meeting outside Bridge ↗
- Bridge help center: Spaces ↗
- Bridge help center: Labels ↗
