
Orchestrate SAFe Program Increment Planning
Coordinate multi-team SAFe PI Planning sessions with dependency tracking
What You Can Do
You can orchestrate end-to-end PI Planning logistics for 5–12 teams across a single Agile Release Train. This skill helps you design the 2-day event agenda, manage team breakout sessions, identify and negotiate cross-team dependencies in real-time, track PI Objectives and team capacity, and produce post-planning artifacts (dependency matrix, PI board, commitment summaries) that keep all teams aligned through the 10-week increment.
Features
structures 2-day (or compressed 1-day) event with keynotes, team planning sessions, dependency resolution, and commitment reviews
facilitates cross-team discussion to surface, visualize, and resolve blocking dependencies before teams commit
balances program goals against team velocity and capacity to prevent overcommitment and ensure achievable PI Objectives
mediates disagreements between teams on shared work, resource allocation, or competing priorities during planning
produces dependency matrix, PI board, team commitment summaries, and risk register with clear ownership
captures planning-process feedback and systemic blockers to improve future PI Planning events
synthesizes PI outcomes for leadership review and ensures business objectives are reflected in team commitments
Example Output
PI Planning Agenda (2-Day Format)
- Day 1 Morning: Business Context & Vision keynote (30 min) → System Demo (30 min) → Team Planning Session 1 (2 hrs) → Lunch
- Day 1 Afternoon: Team Planning Session 2 (2 hrs) → Dependencies Discussion Facilitation (1 hr) → Risk Identification (30 min)
- Day 2 Morning: Cross-team Dependency Resolution Boards (90 min) → Confidence Vote & Risk Review (45 min) → Team Commitment Finalization (45 min)
- Day 2 Afternoon: Executive Briefing & PI Board Review (1 hr) → Retrospective (45 min)
Dependency Matrix Output
| Team A | Team B | Dependency | Type | Owner | Target Sprint | Risk |
|---|---|---|---|---|---|---|
| Mobile App | Backend API | Async Auth API delivery | Blocker | Team B PO | Sprint 1 | Medium — API scope TBD |
| Mobile App | DevOps | Container orchestration readiness | Hard | DevOps | Sprint 2 | Low — in progress |
Team Commitment Summary Team A (5 engineers, 34 pts capacity): 8 PI Objectives, 32 pts committed, 2 pts risk buffer, 1 dependency on Team B Sprint 1
What's Included
- SKILL.md: complete PI Planning orchestration playbook with SAFe governance and dependency management workflows
- PI Planning Agenda Templates: 2-day and compressed 1-day formats with timing, facilitation notes, and breakout session structure
- Dependency Identification Checklist: cross-functional dependency discovery matrix and negotiation protocol
- PI Planning Facilitation Guide: real-time techniques for managing conflict, keeping teams on schedule, and ensuring psychological safety
- Post-Planning Artifacts Kit: PI board template, commitment registry, risk log, and executive briefing slide deck
Who It's For
- Scrum Masters and Agile Coaches — facilitating PI Planning logistics and multi-team coordination for ARTs
- Release Train Engineers (RTEs) — overseeing program-level planning and ensuring alignment with business objectives
- Program Managers — balancing portfolio capacity and dependencies across multiple teams
- Agile Release Train Program Owners — coordinating stakeholder inputs and ensuring PI commitments reflect strategic priorities
Best For
- Running 2-day PI Planning events for 5–12 team ARTs
- Identifying and resolving cross-team dependencies before team commits
- Designing PI Planning agendas and facilitation strategies for large-scale organizations
- Creating post-planning artifacts (dependency matrices, PI boards, commitment registers)
- Managing team capacity planning and preventing overcommitment in Program Increments







