PI Planning was designed for a room: 50–200 people, sticky notes, a physical Programme Board, and two days of face-to-face alignment. Running it remotely requires more facilitation effort, better tooling, and deliberate restructuring of the agenda — not just "the same thing on Zoom." This is the guide for doing it right.
Why Remote PI Planning Fails
Most remote PI Planning failures trace to one of three root causes: Zoom fatigue from 16+ continuous hours of video, the physical Programme Board replaced by a shared document nobody maintains, and breakout rooms that teams treat as optional. Fixing these requires structural changes, not just better video discipline.
Recommended Tool Stack
| Purpose | Recommended Tools | Notes |
|---|---|---|
| Main stage | Zoom Webinar / MS Teams Live | Broadcast model for plenaries |
| Team breakouts | Zoom Breakout Rooms / Gather.town | Persistent rooms teams can return to |
| Programme Board | Miro / Mural | Single source of truth — pre-built template |
| Backlog / Stories | Jira / Azure DevOps | Linked to Miro cards via integration |
| Confidence Vote | Mentimeter / Poll Everywhere | Anonymous voting, real-time results |
| Risk ROAM | Miro ROAM board | Resolved / Owned / Accepted / Mitigated |
| Async pre-work | Loom videos + Confluence | Vision and architecture briefing pre-read |
Revised 2-Day Remote Agenda
Day 1
- 08:30 – Opening (45 min, plenary): Business context, vision, ART objectives. Pre-record the architecture briefing as a Loom video — saves 30 minutes and lets teams rewatch.
- 09:15 – Team Breakout 1 (90 min): Teams draft their PI objectives and initial sprint plan in Miro. RTE and Scrum Masters rotate through rooms.
- 10:45 – Draft Plan Review (30 min, plenary): Each team's SM presents top 3 objectives + top 3 dependencies in 3 minutes. Strict timekeeping essential.
- 11:15 – Dependency Mapping (45 min, cross-team): Teams with inter-dependencies meet in dedicated cross-team breakout rooms. RTE visible on Programme Board.
- 12:00 – Async lunch break (60 min): Teams continue async refinement. Avoid lunchtime plenaries.
- 13:00 – Team Breakout 2 (90 min): Teams refine objectives based on dependency resolution. Risk identification begins.
- 14:30 – Day 1 Close (30 min, plenary): Programme Board walkthrough. RTE highlights key dependencies and unresolved risks.
Day 2
- 08:30 – Final Team Breakout (90 min): Teams finalise sprint plans, complete PI objectives, confirm capacity.
- 10:00 – Risk ROAM (45 min, plenary): RTE facilitates ROAM of all identified programme risks. Each risk gets an owner.
- 10:45 – Final Plan Review (45 min): Each team presents final PI objectives (max 5 per team, 3 min each).
- 11:30 – Confidence Vote: Anonymous fist-of-five via Mentimeter. Target: average 3.5+. If below 3, RTE calls an extended problem-solving session.
- 12:00 – Close and Retrospective (30 min): What worked, what to change for next PI Planning.
Remote facilitation tip: The RTE must stay on the Programme Board in Miro throughout Day 1, not in team breakout rooms. Your job is to see the connections teams cannot see from inside their own room.
Confidence Vote: Interpreting Results
| Average Score | Interpretation | Action |
|---|---|---|
| 4.0 – 5.0 | High confidence | Proceed |
| 3.0 – 3.9 | Moderate confidence | Acknowledge risks, proceed |
| 2.0 – 2.9 | Low confidence | Extended problem-solving session before close |
| Below 2.0 | Serious concern | Reschedule — this PI plan is not ready |