PI planning gets the attention, but the event only goes well if the prep is done. Objectives drafted, features ready, capacity known, dependencies mapped. Release train engineers rebuild that prep list every increment, usually from the last one, usually under time pressure.
Here is how to make the prep the same every time, without changing how your train plans.
What the prep usually includes
Every train is different, but the prep tends to cover:
- Draft PI objectives for each team
- Make sure the top features are refined and sized
- Confirm each team’s capacity for the increment
- Map dependencies between teams
- Collect risks to review during the event
- Handle logistics: room or video link, agenda, who presents
Build it as a template set
In AppsDelivered Templates, create a set with an epic at the top, named PI $pi planning prep. $pi is a custom variable, so the app asks for the increment number when you apply it.
Under the epic, add a work item per prep step. Give team-specific steps one work item per team, with that team’s lead as the assignee.
Apply the set at the start of the prep window, often two to three weeks before the event. Every team gets its work items the same day.
What this does not replace
A template set makes the prep consistent. It doesn’t plan the increment for you, and it doesn’t replace your program board or your planning tool. It makes sure everyone arrives at the event with the same inputs ready.
Improve it each increment
At your inspect and adapt session, ask what was missing from the prep. Add it to the template set. Over a few increments the set becomes your train’s own playbook, and new teams joining the train get it on day one.
SAFe is a registered trademark of Scaled Agile, Inc.



