Virtual PI Planning
Run SAFe PI planning with spatial breakout rooms, shared program boards, and cross-team sync
PI planning is the heartbeat of SAFe. Two days, 8-12 teams, hundreds of decisions. In person, it works because people cluster around tables, scribble on program boards, and grab engineers from other teams for a quick dependency chat between sessions.
On a video call, it's a nightmare. 80 people muted on Zoom while the RTE shares a slide. Breakout rooms feel disconnected. Cross-team conversations require scheduling a separate call. The spontaneous "hey, your team's API change blocks us" hallway moment doesn't happen.
PI planning on Flat.social fixes this. Teams work in audio-isolated zones with whiteboards and sticky notes for their iteration plans. The RTE presents in a Conference room. Between sessions, engineers walk across the spatial room to talk to other teams about dependencies through spatial audio. It's the closest you'll get to a big room planning event without flying everyone to the same office.
Cross-Team Conversations, Naturally
Engineers from different teams talk through dependencies using spatial audio. Voice indicators show who's speaking, and conversations fade naturally with distance. No scheduling a separate call. Just walk over and talk.
What is PI planning in SAFe?
PI (Program Increment) planning is a cadence-based event in the Scaled Agile Framework (SAFe) where all teams in an Agile Release Train align on objectives, identify dependencies, and commit to work for the next 8-12 week increment. It typically runs over 2 days with alternating full-group sessions and team breakouts.
Why Run PI Planning on Flat.social
Walk Between Team Zones
Avatars move closer and the conversation begins. Move away and the audio fades. During dependency sync, engineers walk to other team zones and discuss integration points face to face. It's how hallway conversations happen in a spatial room.
How to Run PI Planning on Flat.social
- 1Set up the PI planning venue
Create a flat with a Main Stage (Conference room for RTE presentations), a Planning Floor (Open Spatial room with team zones), and a Program Board room (Open Spatial with a shared whiteboard). Add a Dependency Discussion area for cross-team sync.
- 2Prepare team zones
On the Planning Floor, create audio isolation zones for each team. Place a whiteboard and sticky notes in each zone. Add a billboard with the team's backlog summary and iteration boundaries. Name each zone clearly (Team Alpha, Team Beta, etc.).
- 3Configure roles
Set up roles: RTE (full admin), Scrum Masters (build mode + manage), Product Owners (build mode), and Team Members (standard access). Assign roles by email in bulk.
- 4Run Day 1
Start on the Main Stage with business context, vision, and architecture review. Move teams to the Planning Floor for team breakouts. Teams plan their first iteration on whiteboards. After breakouts, gather back on the Main Stage for a draft plan review. Use the Dependency Discussion zone for cross-team sync.
- 5Run Day 2
Teams finalize plans in their zones. Cross-team dependency discussions happen in the spatial room between zones. Management reviews plans on the Main Stage. Close with a confidence vote using reactions. Everyone sends fireworks if they're committed.
Run PI Planning That Actually Works Remote
Team breakouts, cross-team sync, and a program board in one spatial venue. Free to start.
PI Planning Sessions on Flat.social
How each session type works in spatial rooms.
RTE presents on the main stage with screen sharing
Shared Whiteboards for Every Team
Each team zone has its own whiteboard and sticky notes. Plan iterations, map dependencies, and track risks visually. Multiple people draw and write simultaneously while discussing through spatial audio.
Tips for Release Train Engineers
Running remote PI planning well takes extra intentionality. Here's what works:
1. Pre-build the entire venue. Don't set up during the event. Have every team zone, billboard, and whiteboard ready before Day 1 starts. Post the agenda at the entrance. When 80 people walk in, they should know exactly where to go.
2. Assign "zone captains." Each Scrum Master owns their team's zone. They manage the whiteboard, update the billboard with the draft plan, and flag when they need a cross-team conversation. It distributes the facilitation load.
3. Schedule explicit dependency sync time. Don't rely on people finding each other organically. Block 30 minutes after each team breakout where everyone is on the Planning Floor and expected to walk between zones. Post a billboard: "Dependency sync. Walk to any team you need to talk to."
4. Use billboards as the program board. Place a large billboard in the Program Board room and update it as teams finalize plans. Everyone can visit the room to see the big picture. It's your agile scrum tools equivalent of a physical board.
5. Run the confidence vote with reactions. It's more engaging than asking people to type a number. The visual burst of 80 reactions tells you instantly where the energy is.
Conference Stage for All Hands
The RTE presents in a Conference room with Speaker layout. Screen sharing handles slides and backlogs. 80 participants watch together, then walk to the Planning Floor for breakouts. The transition feels physical.
Tips for Team Members
Making PI planning productive on Flat.social:
Stay in your zone during breakouts. The audio isolation means your team has a private space. Use it. Plan on the whiteboard, track risks on sticky notes, and keep your camera on so the energy stays high.
Walk to other teams during sync time. If your team depends on another team's work, walk to their zone during dependency sync. A 3-minute face-to-face conversation prevents a month of back-and-forth tickets.
Update the program board. After your team finalizes a plan, add your features and dependencies to the shared program board in the Program Board room. The RTE and management will review it.
Use reactions for the confidence vote. When the RTE calls for the vote, send your reaction immediately. Don't wait. The simultaneous burst is what makes it meaningful. If your confidence is low, speak up during the follow-up discussion.
Virtual PI Planning FAQ
Explore More Use Cases
Plan Your Next PI in Flat.social
Team zones, program boards, dependency sync, and confidence votes. Everything your ART needs to plan effectively. Free to start.