GuideRolesEventsWorkflow

SAFe Events

PI Planning

PI Planning is the signature event of SAFe — a 2-day face-to-face (or virtual) working session where all ART members (50–125+ people) align on a shared vision, identify dependencies, negotiate scope, and commit to PI Objectives. It produces an alignment that cannot be achieved through documents, status meetings, or email.

The signature event · Timebox: 2 days

Overview

PI Planning is the signature event of SAFe — a 2-day face-to-face (or virtual) working session where all ART members (50–125+ people) align on a shared vision, identify dependencies, negotiate scope, and commit to PI Objectives. It produces an alignment that cannot be achieved through documents, status meetings, or email.

Event Ownership

Owned / Facilitated By
Release Train Engineer (facilitator) / Product Management (content authority)
RTE facilitates the overall event: agenda, logistics, timekeeping, and cross-team coordination
Product Management presents the vision, top features, and business context for the upcoming PI
RTE manages the ART Planning Board, consolidates team PI Objectives, and runs the confidence vote
Product Management negotiates scope with teams and resolves feature-level prioritization conflicts

Who Should Be Present

All ART Members
Every team member attends. Teams participate in breakouts, plan their iterations, identify dependencies, and commit to objectives
Product Management
Presents vision and top 10 features. Available throughout for scope questions. Reviews and adjusts PI Objectives
System Architect
Presents architecture vision, enablers, and NFRs. Available during breakouts for technical guidance
Business Owners
Provide business context, participate in objective review, assign business value to PI Objectives, and vote on confidence
RTE
Facilitates all sessions, manages the program board, runs the confidence vote, and facilitates the planning retrospective

Preparation Checklist

01Product Management: ART Backlog prioritized, top features have acceptance criteria, vision presentation ready
02RTE: Logistics arranged (room, tools, agenda), facilitation materials prepared, prior PI metrics gathered
03System Architect: Architecture vision and enabler backlog ready for presentation
04Teams: Capacity calculated (PTO, holidays, support rotations), prior PI retrospective actions reviewed
05Business Owners: Business context and strategic themes prepared for presentation

Facilitation Techniques

Click any technique to expand details and learn when to apply it.

Day 1: Vision → Breakout → Draft Plan

Structure Day 1 as: Business Context presentation, Product/Architecture Vision, then team breakout sessions where teams decompose features into stories and create draft plans. End with a management review of draft plans.

Click to expand

Day 2: Adjust → Final Plan → Confidence Vote

Day 2 begins with adjustments based on Day 1 feedback. Teams finalize plans, update the ART Planning Board with final dependencies, present final PI Objectives, and conduct the confidence vote.

Click to expand

Fist-of-Five Confidence Vote

Every team member votes 1–5 on confidence that the team can achieve its PI Objectives. If anyone votes below 3, discuss and adjust until the team can commit. This is the moment of collective commitment.

Click to expand

ART Planning Board Management

Use a large physical or digital board showing all features across all teams, iteration boundaries, milestones, and dependency strings. Color-code dependencies by risk level. Walk the board daily.

Click to expand

ROAM Risk Classification

Classify each identified risk as Resolved, Owned (someone will handle it), Accepted (we’ll live with it), or Mitigated (action taken to reduce impact). Track ROAM items throughout the PI.

Click to expand

Planning Retrospective

At the end of PI Planning, run a brief retrospective on the planning event itself. What went well? What should we improve for next PI Planning? Capture actions for the RTE.

Click to expand

Tips & Tricks

01
Full Attendance
The #1 rule: everyone must attend. Partial attendance destroys the alignment PI Planning creates
02
Backlog Preparation
Prepare the backlog — if features aren’t refined before PI Planning, teams will spend the event refining instead of planning
03
Strict Timeboxing
Timebox presentations strictly. The value is in breakout collaboration, not in slide decks
04
Planning Board Focus
Make the ART Planning Board the centerpiece. Dependencies that aren’t visible don’t get managed
05
Honest Confidence Vote
Conduct the confidence vote honestly. A pressured ‘4’ is worse than an honest ‘2’ that gets addressed
06
Dry Run
Run a dry run with key facilitators 1–2 weeks before the event to surface logistics issues

Anti-Patterns to Avoid

Pre-PI Planning Readiness: Hold a pre-PI Planning sync 1–2 weeks before. Ensure the ART Backlog is refined, architecture vision is prepared, and all teams have calculated capacity. Surface and resolve logistics issues.
PI Objective Publication: Within 24 hours of PI Planning, publish all team and ART PI Objectives to stakeholders. Make them visible on dashboards and in shared tools. This is the contract for the PI.
Immediate Dependency Follow-Up: Within the first week of the PI, the RTE should confirm all dependency owners and establish communication channels. Dependencies without active management become blockers.

Success Takeaways by Role

What each participant should walk away with when this event is run well.

Teams

Clear iteration plans for the PI; visible dependencies with mitigation strategies; shared commitment to PI Objectives

Product Management

Confidence that the ART understands and can deliver the highest-priority features; realistic scope negotiation

RTE

A populated ART Planning Board; identified risks with ROAM assignments; a planning retrospective producing improvements

Business Owners

Visibility into what the ART will deliver; business value assigned to objectives; confidence in the plan

Cross-Framework Definition
See PI Planning in the glossary
→