
SAFe PI Planning Coordinator
Coordinate SAFe PI Planning events and track cross-team dependencies
What You Can Do
You can orchestrate end-to-end PI Planning events for multiple teams and ARTs, from pre-planning preparation through team commitment documentation. This skill helps you identify cross-team dependencies early, validate capacity constraints, mitigate risks, and produce a comprehensive PI Roadmap and planning artifacts that align the entire program to business objectives.
Features
validates team readiness, historical velocity, and planning conditions before the event
structures PO communication of strategic goals, priorities, and capacity constraints
maps team-to-team and system-to-system dependencies with risk flagging
calculates available capacity by team, accounting for innovation, infrastructure, and risk buffers
generates team-level committed stories, features, and risks tied to PI objectives
identifies integration points and PI-level risks requiring escalation
visualizes committed work, key milestones, and dependency flows for stakeholder communication
captures lessons learned and process improvements for the next PI cycle
Example Output
Pre-Planning Readiness Report:
- Team velocity validation: Team A (42 pts), Team B (38 pts), Team C (35 pts)
- Capacity allocation: 75% committed work, 15% innovation, 10% risk buffer
- Blocker flags: 3 external dependencies on Platform team, 2 infrastructure requests pending
PI Dependency Map:
- Team A → Team B (API contract for payment service, critical path)
- Team C → Team A (data pipeline, can start Week 3)
- Cross-ART sync needed: Reporting team blocks analytics feature for Teams B & C
PI Commitment Summary:
- Team A: 8 features (35 pts), 12 stories (42 pts), Risks: {API delay, resource constraint}
- Team B: 6 features (30 pts), 10 stories (38 pts), Risks: {third-party integration}
- Team C: 5 features (28 pts), 8 stories (35 pts), Risks: {infrastructure provisioning}
What's Included
- SKILL.md instruction file with SAFe PI Planning framework and coordination methodology:
- Pre-Planning Checklist Template: 20-point validation of team readiness and planning conditions
- Business Context Session Agenda: structured PO briefing with strategic alignment and capacity overview
- Dependency Mapping Worksheet: risk-rated cross-team and cross-ART dependencies with mitigation plans
- Capacity Planning Workbook: velocity-based capacity calculation with buffer allocation (innovation, risk, infrastructure)
- PI Commitment Documentation Template: team-level committed features, stories, and risk registry
- PI Roadmap Generator: visual timeline with milestones, dependencies, and stakeholder communication format
Who It's For
- Scrum Masters and Agile Coaches — coordinating PI Planning execution across multiple teams and ARTs
- Release Train Engineers (RTEs) — managing ART-level planning, dependencies, and risk escalation
- Program Managers — ensuring business objectives are mapped to team commitments with visibility
- Product Owners — prioritizing backlog and communicating capacity constraints during planning
- Agile Program Office (APO) leaders — standardizing PI Planning processes across the enterprise
Best For
- Preparing for and executing SAFe Program Increment Planning events (every 8-10 weeks)
- Identifying and visualizing cross-team and cross-ART dependencies before planning begins
- Validating team capacity and building realistic, committed PI plans
- Documenting PI outcomes (roadmap, risks, commitments) for stakeholder visibility
- Improving PI Planning efficiency through structured templates and checklists
- Escalating critical risks and integration points requiring executive attention







