Safe Program Increment Planning Template
📄
💾 Downloadsafe_program_increment_planning_template.md
Markdown • 14,656 bytes
---
title: "Safe Program Increment Planning Template"
methodology: "agile"
complexity: "advanced"
owner: "mirichard"
updated: "2026-09-19"
primary_principles: ["collaborative-leadership", "systems-thinking"]
secondary_principles: ["risk-optimization"]
principle_rationale: "Aligns program vision and team objectives through dependency negotiation, risk review and a confidence assessment of the integrated plan."
---
# SAFe Program Increment Planning Template
## When to Use
- When a SAFe planning interval needs program vision, team objectives, and dependency negotiation.
- When several teams must surface risks and assess confidence in an integrated plan.
## When NOT to Use
- To treat a confidence vote as proof that all delivery risks are controlled.
- Do not use a completed template or example configuration as proof of fitness for the actual environment. See [Template as substitute for judgment](../../../../../../docs/principles/anti-patterns.md#template-judgment).
## Pairs Well With
- [Safe Art Coordination Template](../../../../../../domains/delivery/methodology-frameworks/agile-scrum/scaling-frameworks/safe/safe_art_coordination_template.md).
- [Pi Planning Template](../../../../../../domains/delivery/methodology-frameworks/agile-scrum/scaling-frameworks/safe/pi_planning_template.md).
Selection context: Delivery domain; agile methodology; advanced complexity. Match the situations above to project phase, risk, team size, and industry using the [decision-engine context model](../../../../../../meta/architecture-research/800-801-context-assessment-model.md).
**Agile Release Train:** [ART Name]
**Program Increment:** [PI Number]
**PI Planning Dates:** [Start Date] - [End Date]
**Location:** [Physical Location and/or Virtual Meeting Details]
**Facilitator:** [Name]
**Last Updated:** [YYYY-MM-DD]
## 📋 PI Planning Overview
Program Increment (PI) Planning is a cadence-based collaborative event (in person, distributed, or hybrid) that serves as the heartbeat of the Agile Release Train (ART), aligning all teams to a shared mission and vision. This two-day event brings together all ART members to:
- Align on a common mission and vision
- Identify dependencies and foster cross-team collaboration
- Commit to PI objectives with business value
- Address risks and impediments
- Create team and program plans for the upcoming PI
## 🔄 PI Planning Preparation Checklist
### 2-4 Weeks Before
- [ ] Confirm PI Planning dates and location
- [ ] Reserve venue with adequate breakout spaces
- [ ] Prepare virtual meeting setup if needed
- [ ] Send calendar invitations to all participants
- [ ] Engage with Product Management on vision and priorities
- [ ] Begin preparing feature backlog
### 1-2 Weeks Before
- [ ] Finalize and prioritize Program Backlog
- [ ] Refine Features to INVEST criteria
- [ ] Prepare Business Context presentation
- [ ] Finalize Architecture Vision presentation
- [ ] Create/update Planning Board for dependency tracking
- [ ] Prepare Team Breakout rooms/areas
- [ ] Ensure teams have completed pre-PI Planning backlog refinement
- [ ] Distribute agenda to all participants
### 1-3 Days Before
- [ ] Confirm logistics (room setup, catering, technology)
- [ ] Print physical materials (if applicable)
- [ ] Test all technology platforms
- [ ] Final review of Feature readiness
- [ ] Prepare Risk and Impediment tracking mechanisms
- [ ] Brief facilitators and Scrum Masters on responsibilities
## 📅 PI Planning Agenda
### Day 1
| Time | Activity | Lead | Description |
|------|----------|------|-------------|
| 08:30 - 09:00 | Check-in and Setup | All | Arrival, setup, and networking |
| 09:00 - 09:15 | Welcome and Logistics | RTE | Welcome, agenda review, logistics |
| 09:15 - 09:45 | Business Context | Business Owners | Market trends, business direction, competitive analysis |
| 09:45 - 10:30 | Product/Solution Vision | Product Management | Vision, roadmap, top 10 features |
| 10:30 - 11:00 | Architecture Vision | System Architect | Technical direction, standards, NFRs |
| 11:00 - 11:15 | Planning Context & Guardrails | RTE | Planning process, expectations, constraints |
| 11:15 - 12:00 | Team Breakouts - 1 | Teams | Initial planning, story breakdown |
| 12:00 - 13:00 | Lunch | All | |
| 13:00 - 15:30 | Team Breakouts - 2 | Teams | Continue planning, draft objectives |
| 15:30 - 16:30 | Draft Plan Review | Team Reps | Present draft plans, identify dependencies |
| 16:30 - 17:00 | Management Review | Leadership | Review progress, address blockers |
| 17:00 - 17:30 | Problem-Solving Workshop | As needed | Address major issues identified |
### Day 2
| Time | Activity | Lead | Description |
|------|----------|------|-------------|
| 08:30 - 09:00 | Check-in | All | Day 1 recap, adjustments to plans |
| 09:00 - 11:30 | Team Breakouts - 3 | Teams | Finalize plans, address dependencies |
| 11:30 - 12:30 | Final Plan Review | Team Reps | Present final plans, updated objectives |
| 12:30 - 13:30 | Lunch | All | |
| 13:30 - 14:30 | Program Risks | RTE | Review and address program risks |
| 14:30 - 15:00 | Confidence Vote | All | Teams vote on confidence in the plan |
| 15:00 - 16:00 | Plan Rework (if needed) | Teams | Address concerns from confidence vote |
| 16:00 - 16:30 | Planning Retrospective | All | What went well, what to improve |
| 16:30 - 17:00 | Closing | RTE/Leaders | Final words, next steps, celebration |
## 🎯 Program Vision
### Strategic Themes
- [Theme 1]
- [Theme 2]
- [Theme 3]
### PI Goals
1. [Primary business objective for this PI]
2. [Secondary business objective for this PI]
3. [Additional objectives as needed]
### Key Business Metrics
| Metric | Current | Target | Measurement Method |
|--------|---------|--------|-------------------|
| [Metric 1] | [Value] | [Value] | [Method] |
| [Metric 2] | [Value] | [Value] | [Method] |
| [Metric 3] | [Value] | [Value] | [Method] |
## 📊 Feature List
| ID | Feature | Description | Business Value | Priority | Dependencies | Teams Involved |
|----|---------|-------------|----------------|----------|--------------|----------------|
| F-1 | [Example] User Authentication Enhancements | Implement multi-factor authentication and single sign-on capabilities | High - Security compliance requirement | 1 | Identity Provider API | Auth Team, Security Team |
| F-2 | [Example] Dashboard Redesign | Redesign main dashboard for improved user experience and performance | Medium - Improves user satisfaction | 2 | UX Research completion | UX Team, Frontend Team |
| F-3 | [Example] Reporting API | Develop new API endpoints for enhanced reporting capabilities | High - Strategic customer requirement | 1 | Data warehouse integration | Backend Team, Data Team |
| F-4 | | | | | | |
| F-5 | | | | | | |
| F-6 | | | | | | |
| F-7 | | | | | | |
| F-8 | | | | | | |
| F-9 | | | | | | |
| F-10 | | | | | | |
## 🧩 Team Planning
### Team Capacity Summary
| Team | Members | Days Available | Focus Factor | Story Points Capacity |
|------|---------|----------------|--------------|----------------------|
| [Team 1] | [Number] | [Sum of available days] | [%] | [Capacity in SP] |
| [Team 2] | [Number] | [Sum of available days] | [%] | [Capacity in SP] |
| [Team 3] | [Number] | [Sum of available days] | [%] | [Capacity in SP] |
| [Team 4] | [Number] | [Sum of available days] | [%] | [Capacity in SP] |
| [Team 5] | [Number] | [Sum of available days] | [%] | [Capacity in SP] |
### Team Objectives Template
#### [Team Name]
| ID | Objective | Business Value | Features | Committed (Y/N) | Sprint Alignment |
|----|-----------|----------------|----------|-----------------|------------------|
| [Team]-1 | [Example] Implement user authentication service with SSO support | 10 | F-1 | Y | Iterations 1-2 |
| [Team]-2 | [Example] Complete UX design for new dashboard | 8 | F-2 | Y | Iteration 1 |
| [Team]-3 | [Example] Develop new reporting API endpoints | 7 | F-3 | Y | Iterations 2-3 |
| [Team]-4 | [Example] Implement automated test suite for authentication | 5 | F-1 | Y | Iteration 3 |
| [Team]-5 | [Example] Create documentation for API | 3 | F-3 | Y | Iteration 4 |
| [Team]-S | [Example] Implement additional security scanning | 2 | None - Stretch | N | Iteration 5 |
**Notes:**
- Business Value is on a scale of 1-10, with 10 being highest value
- Include stretch objectives clearly marked with "S" suffix
## 🔄 Dependency Management
### Dependency Board
| ID | From Team | To Team | Description | Required By | Status | Resolution Plan |
|----|-----------|---------|-------------|------------|--------|-----------------|
| D-1 | [Example] Auth Team | Security Team | Security review of authentication flow | Iteration 2 | Open | Security team to prioritize review in Iteration 1 |
| D-2 | [Example] Frontend Team | UX Team | Final design specs for dashboard | Iteration 2 | Open | Daily sync meetings to review progress |
| D-3 | [Example] API Team | Data Team | Data model specifications | Iteration 1 | Resolved | Completed in pre-PI planning |
| D-4 | | | | | | |
| D-5 | | | | | | |
| D-6 | | | | | | |
| D-7 | | | | | | |
| D-8 | | | | | | |
| D-9 | | | | | | |
| D-10 | | | | | | |
### Dependency Visualization
```
[Add a visual dependency map here - can be created during PI planning]
Example:
Auth Team ----> Security Team ----> Compliance Team
| ^
v |
Frontend Team ----> UX Team -------------|
|
v
API Team -----> Data Team
```
## ⚠️ Program Risks and Impediments
### ROAM Board
| ID | Risk/Impediment | Type | Probability | Impact | ROAM Status | Owner | Mitigation Plan |
|----|-----------------|------|-------------|--------|-------------|-------|-----------------|
| R-1 | [Example] Third-party API integration may be delayed | External Dependency | Medium | High | Owned | Integration Lead | Early engagement with vendor, develop fallback plan |
| R-2 | [Example] Team capacity reduced due to planned vacations | Resource | High | Medium | Accepted | Scrum Masters | Adjust capacity planning, identify backup resources |
| R-3 | [Example] New technology stack has learning curve | Technical | Medium | Medium | Mitigated | Architects | Schedule training sessions in first iteration |
| R-4 | | | | | | | |
| R-5 | | | | | | | |
| R-6 | | | | | | | |
| R-7 | | | | | | | |
| R-8 | | | | | | | |
| R-9 | | | | | | | |
| R-10 | | | | | | | |
**ROAM Legend:**
- **Resolved:** The risk has been addressed and no longer exists
- **Owned:** Someone has taken responsibility for resolving the risk
- **Accepted:** The risk cannot be resolved, but the organization accepts it
- **Mitigated:** Action has been taken to reduce the probability or impact
## 🗳️ Confidence Vote
### Team Voting Results
| Team | Vote | Key Concerns | Action Items |
|------|------|--------------|--------------|
| [Team 1] | [1-5] | [Brief description] | [Action items to address concerns] |
| [Team 2] | [1-5] | [Brief description] | [Action items to address concerns] |
| [Team 3] | [1-5] | [Brief description] | [Action items to address concerns] |
| [Team 4] | [1-5] | [Brief description] | [Action items to address concerns] |
| [Team 5] | [1-5] | [Brief description] | [Action items to address concerns] |
**Overall Program Confidence:** [Average score]
**Voting Scale:**
1. No confidence - Will not work, fundamental rework required
2. Low confidence - Might work with significant adjustments
3. Moderate confidence - Should work with minor adjustments
4. High confidence - Plan appears feasible; track identified risks and assumptions
5. Very high confidence - Strong confidence in feasibility; this is not a delivery guarantee
### Plan Adjustments (Post-Vote)
| Adjustment | Rationale | Teams Affected | Implementation Plan |
|------------|-----------|----------------|---------------------|
| [Adjustment 1] | [Rationale] | [Teams] | [Plan] |
| [Adjustment 2] | [Rationale] | [Teams] | [Plan] |
| [Adjustment 3] | [Rationale] | [Teams] | [Plan] |
## 📆 PI Roadmap Calendar
```
[Visual calendar representation of the entire PI]
Example:
Iteration 1 (2 weeks): Jan 10-23
- Auth Team: Authentication foundation
- UX Team: Dashboard design
- API Team: Data model definition
Iteration 2 (2 weeks): Jan 24-Feb 6
- Auth Team: SSO Integration
- Frontend Team: Dashboard implementation start
- API Team: Core endpoints
... and so on
```
## 📝 Post-PI Planning Actions
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|
| Finalize PI Objectives document | RTE | [Date] | [Status] |
| Distribute dependency board to all teams | RTE | [Date] | [Status] |
| Schedule first ART sync | RTE | [Date] | [Status] |
| Update Program Board | Product Management | [Date] | [Status] |
| Communicate plan to stakeholders | RTE/PM | [Date] | [Status] |
| Schedule Innovation & Planning iteration | RTE | [Date] | [Status] |
## 🔍 PI Planning Retrospective
### What Went Well
- [Item 1]
- [Item 2]
- [Item 3]
### What Could Be Improved
- [Item 1]
- [Item 2]
- [Item 3]
### Action Items for Next PI Planning
- [Item 1]
- [Item 2]
- [Item 3]
---
## Appendix A: Role Definitions
- **RTE (Release Train Engineer):** Facilitates the ART process and events, escalates impediments
- **Product Management:** Defines features and participates in planning to provide clarification
- **System Architect/Engineering:** Establishes technical direction and assists teams during planning
- **Business Owners:** Participate in planning, approve plans, and assign business value
- **Scrum Master:** Facilitates team planning, helps coordinate with other teams
- **Product Owner:** Works with teams to define stories and acceptance criteria
- **Development Team:** Defines user stories, estimates, identifies risks and dependencies
## Appendix B: PI Planning Success Factors
1. **Face-to-face participation** (or high-quality virtual experience)
2. **Proper preparation** (features ready, capacity planning done)
3. **Right participants** (all team members, leadership, stakeholders)
4. **Focus on business outcomes** (not just features)
5. **Real-time decision-making** (business owners present)
6. **Commitment-based planning** (not assignment)
7. **Continuous adjustments** during planning
8. **Fast feedback** on plan quality (confidence vote)
---
*This template follows the Scaled Agile Framework (SAFe) PI Planning process. Customize as needed for your organization's specific implementation of SAFe.*