Meeting kit · Strategy & planning
Both days of SAFe PI Planning: a kickoff deck, a program board by iteration, ROAM risks, the fist-of-five confidence vote and a planning retro.
Free to open and edit. Running it live needs Pro, free for 14 days on every new account.
Payments release train · PI 7 · Two days
PI Planning is SAFe's two-day event where every team on an Agile Release Train plans the next PI together. This kit gives you the full two-day agenda, an 11-slide kickoff deck, an ART planning board (the program board) by iteration, ROAM risk handling, a fist-of-five confidence vote on phones and a planning retrospective.
01Inside
Everything one meeting needs: a timed agenda, the slides, a board and the follow-up email.
By the end of this meeting, every team on the train has committed PI objectives, dependencies are on the program board, risks are ROAMed and the train has voted its confidence.
Thank you, everyone. Here's what the train committed to. Confidence vote: average ____ (teams: ______) PI objectives by team (committed / uncommitted, business value) Team ______: ______ Team ______: ______ Train risks (ROAM) Risk | R/O/A/M | Owner ______ | ____ | ______
Key dependencies and milestones: see the program board. What we'll change about next PI Planning: ______ Next: iteration 1 starts ______. System demos every ______. Inspect and adapt in the IP iteration.
02In the room
The shared screen, every phone and the summary afterwards, drawn from this template.
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.
03How to run it
Test video, audio and the board before day 1. Tech failures are one of the most common PI Planning problems.
This kit covers both days; the PI Planning day 1 agenda covers only the first. End day 1 after the management review and continue on day 2 at planning adjustments.
Teams place features, dependencies and risks on the program board from their phones during breakout 1, so the draft plan review sees one board.
Run the fist-of-five vote openly. If the average is low or people vote 1 or 2, hear their concerns and rework the plan.
Send PI objectives, ROAMed risks and the confidence result from the follow-up before teams leave.
04Questions
Still deciding?
Run your next meeting on it. Every new account gets Pro free for 14 days, no card.
Day 1: business context, product vision, architecture vision, planning context, team breakouts, draft plan review and management review. Day 2: planning adjustments, team breakouts, final plan review, train risks, the confidence vote, plan rework if needed and a planning retrospective.
A fist-of-five vote at the end of day 2: everyone shows one to five fingers for confidence in the plan. Low votes are discussed and can lead to plan rework.
Resolved, Owned, Accepted, Mitigated: the four categories each train-level risk is placed in so nothing is left unaddressed.
The structure, wording and safety points in this template follow these published sources.
Keep going
Change anything in the editor. When you're ready, press Run live: everyone joins with a scan and answers on their phone.
Free forever · Pro free for 14 days · No card needed · Guests never sign up
PI Planning kit (SAFe, two days)Runs with Pro