Agenda · Planning
Day one of SAFe PI Planning: business context, product vision, architecture vision, team breakouts and a draft plan review.
Opens in the builder. No sign-up to try it; free forever to run it live.
By the end of this meeting: Every team on the train understands the business context and vision and has a draft plan for the PI.
01Inside
7 blocks in 480 minutes, in order, with the facilitator's tips.
02Why it works
195 minutes of updates with a visible clock. In a video call the speaker is spotlighted and the room is muted, so nobody talks over them.
Cameras pause and the timer keeps running, so the break finishes on time and everyone comes back together.
Everyone types at once and ideas land on the shared screen together. The quiet person's idea gets the same space as everyone else's.
60 minutes of open floor with a countdown everyone can see, and a talk-balance meter so the loudest voice doesn't take all of it.
03In the room
The shared screen, every phone and the summary afterwards, drawn from this agenda.
On the shared screen
Each block runs on its own timer on the shared screen, and the video call changes with each block, so the meeting keeps to time.
On every phone
People scan the code or tap their invite and answer in the phone's browser. No app to install, no account to make.
Afterwards
Decisions and actions are captured as they're said. When the meeting ends, everyone gets the summary, and one link shares it.
04How to run it
Run PI Planning every 8 to 12 weeks; plan two days, or three to four for distributed trains.
Test video, audio and planning boards beforehand; tech failures are a common pitfall.
Keep the business context and vision presentations short so teams stay engaged.
In breakouts, have each team work out its capacity, draft stories and surface dependencies.
Timebox the draft plan review tightly, especially with 10 or more teams.
05Questions
Still deciding?
Run your next meeting on it. Every new account gets Pro free for 14 days, no card.
Two days in SAFe; distributed teams may need three to four days. It runs every 8 to 12 weeks, often quarterly.
Business context, product vision and roadmap, architecture vision, team breakouts on capacity, stories and dependencies, then a draft plan review.
The Release Train Engineer, with the whole Agile Release Train taking part.
The structure, timings and tips on this page come from these sources.
Keep going
Open it in the builder, adjust the minutes, press Run live. Everyone joins with a scan.
Free forever · Pro free for 14 days · No card needed · Guests never sign up
PI Planning day 1 (SAFe)480 minutes · Free template