Pre-PI Planning is where successful PI Planning truly begins. Before teams enter the room for their Program Increment session, the groundwork must be laid: goals clarified, dependencies discussed, and priorities aligned.
Without this preparation, PI Planning risks confusion and wasted effort.
In this guide, you’ll learn exactly what Pre-PI Planning involves, when to run it, who should attend, and how to prepare step-by-step. You’ll also find a practical checklist, visual timeline, and best practices that simplify the process.
Whether you’re a Release Train Engineer, Product Manager, or Scrum Master, this guide will help you run Pre-PI Planning sessions that lead to confident, aligned, and productive PIs.
What Is Pre-PI Planning in SAFe?
Pre-PI Planning is the preparation phase that sets the stage for a productive PI Planning event. It aligns key stakeholders, clarifies objectives, and ensures the Agile Release Train is ready to collaborate effectively.
Without it, teams often walk into PI Planning unprepared, leading to unclear commitments and misaligned priorities.
Definition of Pre-Pi Planning
In the Scaled Agile Framework (SAFe), Pre-PI Planning brings together business owners, Product Management, and System Architects to prepare for the upcoming Program Increment. It focuses on strategy, dependencies, and priorities.
This session typically happens two to four weeks before the main PI Planning event, giving leadership time to frame the work properly.
Importance of Pre-Pi Planning
Thorough Pre-PI Planning eliminates surprises, reduces rework, and enables teams to focus on solution building instead of last-minute alignment. It’s the difference between reactive planning and proactive leadership.
Teams that skip this step often spend the first half of PI Planning catching up on conversations that should have already happened.
Objectives of Pre-PI Planning
The success of PI Planning depends on achieving specific outcomes in Pre-PI Planning. These objectives create alignment across teams and stakeholders.
Core Objectives
Pre-PI Planning focuses on several critical goals that prepare the ART for execution. Here’s what teams should aim to accomplish:
-
•
Establish a shared vision. Ensure everyone understands business and technical goals for the upcoming increment. This means translating portfolio strategy into language that teams can actually plan against, not just abstract business objectives.
-
•
Identify dependencies. Surface inter-team and system-level dependencies early so they don’t become blockers during execution. Dependencies discovered during PI Planning are expensive; dependencies discovered during the sprint are catastrophic.
-
•
Prioritize features. Build a realistic, value-driven Program Backlog that reflects both business priorities and technical capacity constraints.
-
•
Estimate capacity. Align team capacity with upcoming workload, accounting for holidays, planned absences, and other known constraints.
-
•
Assess risks. Document and mitigate early risks before they turn into issues that derail the PI.
-
•
Clarify roles and expectations. Define how each stakeholder contributes to PI success, avoiding overlap and confusion.
-
•
Draft a preliminary Program Board. Create an early visual of objectives and links for later refinement during the main event.
When to Run Pre-PI Planning
Pre-PI Planning happens shortly before the main PI Planning session, usually two to four weeks in advance, depending on the organization’s cadence.
The exact timing varies based on ART maturity and complexity. Some organizations run it as a half-day session, while others need a full day or even multiple sessions spread across a week.
Recommended Timing for Pre-Pi Planning
Conduct it near the end of the current PI or integrate it with the Inspect & Adapt workshop. This timing ensures insights and metrics from the current PI inform the next.
You’re working with real data about what actually happened, not assumptions about what might happen. It also means the leadership team has fresh context from retrospectives and demos.
Indicators that pre-Pi Planning is Needed
Run Pre-PI Planning if teams are new, dealing with major dependencies, or transitioning into new release trains.
It’s also essential when organizational goals or external commitments have changed. If leadership can’t clearly articulate the PI objectives two weeks out, that’s a signal you need more preparation time, not less. The same applies when you’re coordinating multiple ARTs or solution trains.
Pre-PI Planning Step-by-Step Process
Running effective Pre-PI Planning follows a structured sequence. Below is the step-by-step approach teams can replicate before every Program Increment.
These steps build on each other, so skipping one usually creates problems downstream. The process typically takes four to six hours, depending on ART complexity and organizational maturity.
1. Establish a Timeline
Start by defining the PI dates, then work backward to schedule your Pre-PI session. Include time for dependency mapping, feedback review, and draft Program Board creation.
Most teams need at least two weeks between Pre-PI and PI Planning to socialize outcomes and adjust based on feedback. Mark key milestones on a shared calendar.
2. Identify Stakeholders
List participants such as Business Owners, Product Managers, Architects, RTEs, and select Scrum Masters. Keep the group small enough for decision-making but broad enough for coverage.
You want the people who can commit resources and make trade-offs, not just observers or note-takers. Typically this means eight to fifteen people maximum.
3. Define Objectives
Agree on strategic goals and what success looks like. Align these with portfolio or solution roadmaps so that PI Planning starts with shared clarity.
If business owners can’t agree on priorities here, they definitely won’t agree under the pressure of a two-day planning event. Write objectives in measurable terms.
4. Gather Inputs
Review business metrics, backlog items, architecture enablers, and lessons learned. Pull feedback from customers, previous retrospectives, and the Inspect & Adapt workshop.
This is where you transform qualitative insights into quantitative priorities that teams can actually plan against. Don’t skip the data review.
5. Prioritize Features
Facilitate a backlog prioritization discussion between Product Management and Architecture. Use weighted shortest job first (WSJF) or another method to finalize a Program Backlog draft. The goal is a ranked list that balances business value with technical feasibility and risk.
6. Communicate Expectations
Share the Pre-PI outcomes with all ART teams: objectives, priorities, and dependencies.
Use visual summaries or slide decks to ensure alignment ahead of the main PI Planning event. Don’t assume people will read long emails or documents. Make it scannable and visual.
Pre-PI Planning Checklist
A checklist helps maintain consistency and saves time across PIs. Below is a reusable Pre-PI Planning preparation checklist. You can adapt this to fit your organization’s specific context and tooling.
Checklist
Use this list to track your Pre-PI Planning preparation and ensure nothing critical gets missed:
-
☐
Confirm PI Planning date and ART schedule
-
☐
Define draft business and technical objectives
-
☐
Review performance metrics and customer feedback from the current PI
-
☐
Identify dependencies and risks across teams and systems
-
☐
Prioritize features and enablers using WSJF or another agreed method
-
☐
Validate capacity and team availability, accounting for holidays and known absences
-
☐
Review lessons from the last PI, especially blockers and what slowed delivery
-
☐
Align Product Management and System Architecture on priorities and trade-offs
-
☐
Prepare Program Board draft with initial objectives and dependencies mapped
-
☐
Circulate agenda and participant list at least one week before the session
-
☐
Set up communication channels and tools like Miro, Jira, or your preferred platform
-
☐
Schedule follow-up for feedback and improvement after PI Planning completes
Benefits of Pre-PI Planning
Pre-PI Planning adds measurable value to the PI process by reducing confusion and improving decision-making. Teams that invest in this preparation consistently outperform those that skip it.
Key Benefits
Here’s what effective Pre-PI Planning delivers to your Agile Release Train:
-
•
Ensures alignment between business and technical leaders. Everyone enters PI Planning with a shared understanding of goals, not competing interpretations of strategy.
-
•
Reduces risk and dependency conflicts before execution. You surface blockers when there’s still time to solve them, not during sprint two when it’s too late.
-
•
Improves PI Planning efficiency and focus. Teams spend less time debating priorities and more time building realistic plans they can commit to.
-
•
Increases stakeholder engagement and accountability. When leaders participate in preparation, they stay engaged through execution and remove obstacles faster.
-
•
Builds confidence in team commitments. Teams can make honest commitments because they understand what’s expected and what resources they have available.
-
•
Enables data-driven prioritization and resource allocation. Decisions are based on capacity, velocity, and actual constraints, not wishful thinking or political pressure.
-
•
Enhances adaptability for changing goals. A solid foundation makes it easier to pivot when business conditions shift mid-PI.
-
•
Strengthens collaboration across ARTs and portfolios. Cross-train visibility improves when preparation happens at the leadership level first.
Common Challenges in Pre-PI Planning
Even experienced SAFe teams face issues during Pre-PI Planning. Knowing them in advance helps you mitigate problems before they derail planning. Most challenges stem from unclear ownership or rushed execution.
Typical Challenges
Here are the problems teams encounter most often during Pre-PI Planning sessions:
-
•
Unclear objectives. Lack of direction leads to scattered priorities and teams planning work that doesn’t align with business goals or strategy.
-
•
Inadequate preparation. Teams arrive without backlog refinement or metrics, forcing the session to become a working meeting instead of a decision-making forum.
-
•
Conflicting priorities. Portfolio and team goals misaligned, creating tension between what leadership wants and what teams can realistically deliver.
-
•
Low engagement. Stakeholders treat sessions as formality rather than critical preparation, leading to surface-level discussions that don’t resolve real issues.
-
•
Dependency overload. Too many cross-team blockers remain unresolved because the right people aren’t in the room or dependencies weren’t mapped early enough.
-
•
Time constraints. Compressed sessions limit discussion and analysis, forcing teams to rush through critical decisions that need more thoughtful consideration.
-
•
Poor facilitation. Rushed or unfocused facilitation reduces effectiveness and allows dominant voices to control outcomes without proper debate or input from the full group.
Best Practices for a Successful Pre-PI Planning Session
These proven tips help teams conduct Pre-PI Planning that’s organized, collaborative, and insightful. Apply them consistently and you’ll see better outcomes across every PI.
1. Involve the Right People
Include key decision-makers early. The right mix of business, architecture, and delivery stakeholders prevents rework and aligns top-down and bottom-up planning.
If someone has veto power over priorities, they need to be in the room during Pre-PI, not hearing about decisions secondhand.
2. Foster Transparency
Encourage open sharing of risks, dependencies, and lessons learned. Use collaboration tools to capture issues in real time.
Create psychological safety so people feel comfortable surfacing problems early rather than hiding them until they become crises during execution. The Agile Alliance offers helpful guidance on facilitation techniques that promote transparency.
3. Leverage Data and Metrics
Base discussions on actual velocity, predictability, and customer data. Quantitative insight turns subjective debate into informed prioritization.
Review sprint completion rates, defect trends, and customer satisfaction scores before making commitments about what the next PI can deliver.
4. Keep Sessions Focused
Set a clear agenda with time limits for each topic. Pre-PI Planning can easily drift into problem-solving mode when the real goal is preparation and alignment, not solving every issue on the spot.
Pre-PI Planning vs PI Planning
While both are vital parts of SAFe’s cadence, Pre-PI and PI Planning serve different purposes and involve different participants.
Understanding the distinction helps you allocate time and resources appropriately. Many teams blur these sessions together or skip Pre-PI entirely, then wonder why PI Planning feels chaotic and unproductive.
Key Differences
Here’s how Pre-PI Planning and PI Planning compare across critical dimensions:
| Aspect | Pre-PI Planning | PI Planning |
|---|---|---|
| Timing | 2–4 weeks before PI | Start of each PI |
| Focus | Strategic preparation and dependency review | Tactical planning and team commitment |
| Participants | ART leadership, Product Management, Architects | All teams in the Agile Release Train |
| Output | Draft objectives, backlog priorities, and dependencies | Finalized PI plan and committed objectives |
Pre-PI Planning sets the stage. PI Planning executes on that foundation. When Pre-PI is done well, PI Planning becomes a refinement process rather than a starting-from-scratch scramble.
Teams can focus on breaking down features and identifying risks instead of debating which objectives matter most or discovering major dependencies for the first time.
Learn more about how teams build commitment during the planning event in our guide to the Confidence Vote in PI Planning.
Conclusion
Pre-PI Planning lays the foundation for a seamless PI Planning experience. It transforms strategy into actionable preparation, aligns leadership, and resolves major dependencies before the event begins.
By running structured Pre-PI sessions, using checklists, and documenting outcomes, teams can enter PI Planning with shared confidence and focus.
Organizations that invest time here consistently achieve higher predictability and stronger delivery outcomes across Program Increments. The difference shows up in team morale, commitment quality, and the ability to adapt when circumstances change mid-PI.
Start your next PI with proper preparation. Your teams will thank you when planning runs smoothly and execution stays on track.
Want to go deeper into PI Planning best practices? Read our complete PI Planning Guide for end-to-end coverage of the entire planning event.
Looking for hands-on facilitation training? Explore professional SAFe and Agile workshops that build your skills in leading successful planning sessions.
FAQs About Pre-PI Planning
What is the main purpose of Pre-PI Planning?
The main purpose is to align leadership on strategic objectives, priorities, and dependencies before the full ART gathers for PI Planning. It ensures teams enter the main event with clear direction rather than discovering goals during the session itself.
Who attends Pre-PI Planning sessions?
Attendees typically include the Release Train Engineer, Product Management, System Architects, Business Owners, and select Scrum Masters.
The group should be small enough to make decisions quickly but include everyone with authority over priorities and resources.
How far ahead should Pre-PI Planning be scheduled?
Schedule Pre-PI Planning two to four weeks before the main PI Planning event. This gives enough time to communicate outcomes, gather feedback, and make adjustments without rushing the process or letting momentum fade.
How does Pre-PI Planning link to Inspect & Adapt?
Many organizations combine Pre-PI Planning with the Inspect & Adapt workshop at the end of the current PI. This approach uses fresh retrospective data and lessons learned to inform priorities for the next increment.
Can distributed teams run effective Pre-PI sessions remotely?
Yes, distributed teams can run effective Pre-PI Planning remotely using collaboration tools like Miro, Mural, or Microsoft Teams. The key is having a skilled facilitator, a clear agenda, and visual tools that keep everyone engaged and aligned.
![Tuyota Manuwa [SAFe, CSM, PSM, Agile PM, PRINCE2]](https://secure.gravatar.com/avatar/db5d7f9dcb30834fa1a2233afd2599baed692852fbfb7acddda0272c1a52bb7c?s=120&d=mm&r=g)
