12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

___
Introducing the new SAFe Big Picture and enhanced framework articles

+ Framework

ENGLISH (US)

Home » PI Planning

PI Planning

“ Future product development tasks can’t be predetermined. Distribute planning and control to those
who can understand and react to the end results.

—Michael Kennedy, Product Development for the Lean Enterprise [1]

Definition: PI Planning is a cadence-based event for the entire ART that aligns teams and stakeholders to a shared mission
and vision.

Summary
PI Planning is an event that ensures all the teams on an ART, stakeholders, and leaders are aligned to a shared mission
and vision. It is typically a 2-day event for the entire ART that takes place every 8-12 weeks. During this event, all the
teams on the Agile Release Train work collaboratively to create a plan to deliver the highest value work in the
upcoming PI and commit to a set of PI Objectives. PI Planning is led by the Release Train Engineer (RTE). The event
takes place in the Innovation and Planning Iteration, which provides time and space for planning without impacting
delivery.

What is PI Planning?
PI Planning is a cadenced event used for an Agile Release Train (ART) to align Agile Teams and ART leadership to a shared
mission, vision, and committed plan. PI planning is essential in SAFe.

PI planning delivers many business benefits, including:

Establishing face-to-face communication among all Agile Team members and stakeholders
Aligning development to business goals with the business context, vision, and Team and ART PI objectives
Identifying dependencies and fostering cross-team and cross-ART collaboration
Providing the opportunity for just the right amount of architecture and Lean User Experience (UX) guidance
Matching demand to capacity and eliminating excess Work in Process (WIP)
Making fast decisions
Creating a wholistic, transparent view of where and when value will be delivered

Where possible, everyone is physically together. It may not always be practical for the entire Agile Release Train (ART) to
collocate. While physical face-to-face planning has benefits, the focus is that the people who do the work plan the work.
https://scaledagileframework.com/pi-planning/ 1/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework
Real-time, virtual, face-to-face planning has also proven effective when physical presence is not possible as long as all
members of the ART are participating.

How does an ART prepare for PI Planning?

PI planning is a significant event that requires preparation, coordination, and communication. It is facilitated by the RTE.
Event attendees include Business Owners, Product Management, all Agile Teams, System and Solution Architects, and other
stakeholders. The RTE must schedule PI planning events far enough in advance to ensure attendance. The active
participation of Business Owners in this event provides an essential guardrail on budgetary spending.

Inputs to PI planning include:

Business context
Roadmap and vision
Highest priority Features of the ART Backlog

A successful PI planning event delivers two primary outputs:

Committed PI objectives – Each team creates a set of PI objectives with a business value assigned by the Business
Owners.
ART planning board – Identifying new feature delivery dates, feature dependencies among teams, and relevant
milestones

For the event to be successful, preparation is required in three major areas:

Organizational readiness
Content readiness
Logistics readiness

The following sections describe these three areas.

https://scaledagileframework.com/pi-planning/ 2/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

Organizational readiness

Before PI planning, there must be strategy alignment among participants, stakeholders, and Business Owners. Critical roles
are assigned. To address this in advance, however, event organizers must consider the following:

Planning scope and context – Is the planning process’s scope (product, system, technology domain) understood?
Do we know which teams need to plan together?
Business alignment – Is there reasonable agreement on priorities among the Business Owners?
Agile teams – Do we have Agile teams? Are there dedicated team members and an identified Scrum Master/Team
Coach and Product Owner for each team?

Content readiness

It’s equally important to have a clear vision and context so that the right stakeholders can participate. Therefore, the PI
planning must include the following:

Executive briefing – A briefing that defines the current business context

Product vision briefing(s) – Briefings prepared by Product Management, including the top 10 features in the ART
Backlog
Architecture vision briefing – A presentation made to communicate new enablers, features, current and future
state architecture, and Nonfunctional Requirements (NFRs) related to the coming PI

Logistics readiness

Preparing an event to support a large number of attendees isn’t trivial. This prep can include securing and preparing the
space for physically collocated planning. For remote attendees or a fully distributed PI Planning, this also includes
investment in the necessary technical infrastructure. Considerations include:

Locations – Each location where planning takes place needs preparation in advance.
Technology and tooling – Real-time access to information and tooling to support distributed planning or remote
attendees
Communication channels – Primary and secondary audio, video, and presentation channels must be available

This article focuses on the planning activities of a single ART. However, large value streams may contain multiple ARTs and
suppliers. In this case, multiple PI Planning events may need coordination. Further information on how to coordinate at this
scale is found in Pre-Planning and Coordinate and Deliver guidance articles.

Read more about the ART Backlog and Vision:

ART Backlog

Vision

How to run a PI Planning event?

https://scaledagileframework.com/pi-planning/ 3/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework
PI Planning has a standard agenda that begins with a presentation of the business context and vision. This is followed by
team breakouts—where the teams create high-level iteration plans and committed objectives for the upcoming PI.
Facilitated by the Release Train Engineer (RTE), this event includes all members of the ART and occurs within the Innovation
and Planning (IP) Iteration.

PI Planning occurs in a special iteration timebox called the IP Iteration. This avoids affecting the capacity of other iterations
the Agile Teams are delivering within. PI Planning takes two days, although the ART can extend this timebox to
accommodate planning across multiple time zones.

The event follows an agenda similar to Figure 1. Descriptions of each item follow.

Day 1 Agenda Day 2 Agenda

8:00 - 9:00 Business Context 8:00 - 9:00 Planning Adjustments

9:00 - 10:30
Product/Solution
Vision
9:00 - 11:00 Team Breakouts
Architecture Vision
10:30 - 11:30 and Development
Practices

Planning Context Final Plan Review

11:00 - 1:00
11:30 - 1:00 and Lunch
and Lunch

1:00 - 2:00 ART Risks

1:00 - 4:00 Team Breakouts
2:00 - 2:15 Confidence Vote

2:15 - ??? Plan Rework?

4:00 - 5:00 Draft Plan Review
Planning
Management Review Retrospective and
5:00 - 6:00 Moving Forward
and Problem Solving
© Scaled Agile, Inc.

Figure 1. Standard two-day PI planning agenda

Day 1 Agenda

Business context – A Business Owner or senior executive describes the current state of the business, shares the
portfolio vision, and presents a perspective on how effectively existing solutions address current customer needs.
Product/solution vision – Product Management presents the current vision (typically represented by the top ten or
so upcoming features). They highlight changes from the previous PI planning event and any relevant milestones.
Architecture vision and development practices – The System Architect presents the architecture vision. Also, a
senior development manager may introduce Agile-supportive changes to development practices, such as test
automation, DevOps, Continuous Integration, and Continuous Deployment, which the teams will adopt in the
upcoming PI.
Planning context and lunch – The RTE presents the planning process and expected outcomes.
Team breakouts #1 – In the breakout, teams estimate their capacity for each Iteration and identify the backlog
items they will likely need to realize the features (Figure 2). Each team creates draft plans, visible to all, iteration by
iteration.

https://scaledagileframework.com/pi-planning/ 4/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

Figure 2. An Agile Team breakout

During this process, teams identify risks and dependencies and draft their initial team PI objectives. The PI objectives
typically include ‘uncommitted objectives,’ which are goals built into the plan (for example, stories that have been defined
and included for these objectives) but are not committed to by the team because of too many unknowns or risks.
Uncommitted objectives are not extra things to do in case there is time. Instead, they increase the reliability of the plan and
give management an early warning of any objectives that the ART may not be able to deliver. The teams also add the
features and associated dependencies to the ART Planning Board, as shown in Figure 3.

Iteration 1.1 Iteration 1.2 Iteration 1.3 Iteration 1.4 Iteration 1.5 (IP) PI 2 >>>

Milestones &
Events

Unicorns
A milestone or event is
Lions occurring in iteration 1.3
(e.g., release, trade
Bears show)

Eagles

Tigers
This feature cannot be
delivered until multiple
Antelopes teams complete their
dependencies
Bulls

UX Help
A feature with no strings
means it does not have
Sys Arch Help any dependencies

ART Planning Board Legend:

Red strings (or lines for digital boards) are used
Significant Milestone or to connect a feature or milestone to one or more
Features Dependency Event dependencies. Sometimes a dependency has its
own dependencies (see Lions in iteration 1.2)
Blue Red or Pink Orange © Scaled Agile, Inc.

Figure 3. ART planning board showing features and dependencies

https://scaledagileframework.com/pi-planning/ 5/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

Draft plan review – During the tightly timeboxed draft plan review, teams present key planning outputs, which
include capacity and load, draft PI objectives, potential risks, and dependencies. Business Owners, Product
Management, and other teams and stakeholders review and provide input.
Management review and problem-solving – Draft plans likely present challenges like scope, people and resource
constraints, and dependencies. During the problem-solving meeting, management may negotiate scope changes
and resolve other problems by agreeing to various planning adjustments. The RTE facilitates and keeps the primary
stakeholders together for as long as necessary to make the decisions needed to reach achievable objectives.

Note: Solution Trains often hold an additional management review and problem-solving workshop after the first day of
planning to address cross-ART issues. Alternatively, the RTEs of the involved trains may talk with each other to discuss the
problems for the ART’s specific management review and problem-solving meeting. The Solution Train Engineer (STE) helps
facilitate and resolve issues across the ARTs.

Day 2 Agenda

Planning adjustments – The next day, the event begins with management presenting changes to the planning
scope, people, and resources.
Team breakouts #2 – Teams continue planning and making the appropriate adjustments. They finalize their
objectives for the PI, to which the Business Owners assign business value, as shown in Figure 4.

Objectives for PI 1 BV AV

1. Show routing calculations between

the five most frequent destinations 10
2. Navigate autonomously from
distribution center to the most
frequent destination 4
3. Parallel park for a delivery 7
4. Return to the distribution center
after delivery 10
5. Include traffic data in route planning 7
6. Recall a delivery that is already
in progress 8

Uncommitted Objectives
7. Spike: Reduce GPS signal loss by 25% 6
8. Demonstrate real-time rerouting to avoid
delays (e.g., accident, construction) 5

© Scaled Agile, Inc.

Figure 4. A team’s PI objectives sheet with assigned business

value

Final plan review and lunch – All teams present their plans to the group during this session. At the end of each
team’s time slot, the team states its risks and impediments and provides the risks to the RTE for use later in the
ROAMing exercise. Each Agile Team then asks the Business Owners if the plan is acceptable. If the plan is accepted,
the team brings their team PI objective sheet to the front of the room so everyone can see the aggregate objectives
unfold in real-time. If the Business Owners have concerns, teams can adjust the plan to address the identified issues.
The team then presents its revised plan.
ART PI Risks – During planning, teams have identified risks and impediments that could impact their ability to meet
their objectives. These are resolved in a broader management context before the whole train. One by one, the risks
are discussed and addressed with honesty and transparency and then grouped into one of the following categories:
Resolved – The teams agree that the risk is no longer a concern

https://scaledagileframework.com/pi-planning/ 6/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

Owned – Someone on the ART owns the risk since it cannot be addressed during PI planning
Accepted – Some items are simply facts or potential problems that must be understood and accepted
Mitigated – Teams identify a plan to reduce the impact of the risk

Risks
R esolved O wned

A ccepted M itigated

© Scaled Agile, Inc.

Figure 5. Example ROAM Board

A confidence vote in two parts – To gauge readiness for the final plan review, each team conducts a voting
mechanism called ‘fist of five’ physically or in a digital tool. This first vote often occurs during the last team breakout.
Additionally, once ART PI risks have been addressed, the entire ART conducts a ‘fist of five’ physically or in a digital
tool. If the average is three or above, then management should accept the commitment. If it’s less than three, the
ART may need to rework its plan. Anyone voting two or fewer should be allowed to voice their concerns. These
concerns might add to the risk list, require replanning, or provide information.

The Agile Teams and the ART complete a confidence vote that indicates the following commitment:

1. Teams agree to do everything in their power to meet the agreed-to objectives.

2. In the event that objectives are not achievable, teams agree to escalate immediately so that corrective
action can be taken.

Plan rework – If necessary, teams adjust their objectives until the ART has high confidence. This additional planning
is one occasion where alignment and commitment are valued more highly than adhering to a timebox.
Planning retrospective and moving forward – Finally, the RTE leads a brief retrospective for the PI planning event
to capture what went well, what didn’t, and what to do better next time.

Read more for guidance on adapting this agenda to support planning across multiple time zones:

Distributed PI Planning with SAFe

What happens after PI Planning?

Next steps – Typically, a discussion about the next steps, along with final instructions to the teams, follows, including:

Cleaning up the rooms used for planning (if applicable)

https://scaledagileframework.com/pi-planning/ 7/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

Entering the team PI objectives and stories in Agile lifecycle management (ALM) tooling
Reviewing team and ART events calendars
Determining Iteration Planning and Team Sync locations and timing

After the planning event, the RTE and other ART stakeholders summarize the individual team PI objectives into a set of ART
PI objectives (Figure 6) and use this to communicate externally and track progress toward the goals.

Product Management refines the roadmap using the ART PI objectives, improving the forecast for the following PIs.

ART PI Objectives

• Deliver basic search,

sort, and view of books in
inventory
• Deliver basic shopping
cart, purchase and
shipping options
• Support investor demo by
start of iteration 3

Team PI Objectives

Team A BV Team B BV Team C BV Team D BV

• One-click search for 10 • Purchase books 10 • Allow users to 8 • Provide book detail 10
books by title, author via various credit comment on books to web users
and genre card types they have purchased • Allow registered 8
• Support investor 9 • Allow customers to 8 • Support investor 9 users to manage
demo by start of choose their optimal demo by start of their profile
iteration 3 shipping option iteration 3 • Support investor 9
• Drag and drop 3 • Support investor 9 • Implement type- 3 demo by start of
columns by attribute demo by start of ahead using index iteration 3
iteration 3 from search

© Scaled Agile, Inc.

Figure 6. ART PI objectives

Teams leave the PI planning event with a prepopulated backlog for the upcoming PI. They take their team’s PI objectives,
plans, and risks to their regular work area or update their digital tool to accurately reflect the plan. ART risks remain with
the RTE, which ensures that the people responsible for owning or mitigating a risk have captured the information and are
actively managing the risk. The ART Planning Board is maintained physically or digitally throughout the PI to enable
dependency and milestone management.

Most importantly, the ART executes the PI, tracking progress and adjusting as necessary as new knowledge emerges.
Execution of the PI begins with all the teams conducting planning for the first iteration, using their PI plans as a starting
point. It offers fresh input for the iteration planning processes that follow. Since the plans created during PI Planning did
not consider detailed story-level acceptance criteria, the team will likely adjust the first and subsequent iteration plans.

Read more about creating and communicating with PI Objectives:

https://scaledagileframework.com/pi-planning/ 8/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

PI Objectives

References

[1] Kennedy, Michael. Product Development for the Lean Enterprise. Oaklea Press, 2003.

In this article

What is PI Planning?
How does an ART prepare for PI Planning?
How to run a PI Planning event?
What happens after PI Planning?

Key Takeaways

PI Planning is a critical event in SAFe

where Agile Teams and stakeholders align
as an Agile Release Train (ART) around a
shared mission and plan.
PI Planning provides the opportunity to
align development objectives with
business goals, identify dependencies, and
plan work based on available capacity.
Preparation involves ensuring
organizational, content, and logistics
readiness.
PI Planning outputs include committed PI
objectives from the Agile Teams and an
ART planning board that reflects feature
delivery dates and dependencies.

https://scaledagileframework.com/pi-planning/ 9/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

Last update: 15 October 2024

The information on this page is © 2010-2024 Scaled Agile, Inc. and is protected by US and International copyright laws. Neither images nor text can be copied from
this site without the express written permission of the copyright holder. Scaled Agile Framework and SAFe are registered trademarks of Scaled Agile, Inc. Please visit
Permissions FAQs and contact us for permissions.

Framework

Download SAFe Posters & Graphics

Blog

Training

Course Calendar

About Certification

Become a Trainer

Content & Trademarks

FAQs on how to use SAFe content and trademarks

Permissions Form

Usage and Permissions

https://scaledagileframework.com/pi-planning/ 10/11
12/7/24, 9:34 AM PI Planning - Scaled Agile Framework

Scaled Agile, Inc

Contact Us

5400 Airport Blvd., Suite 300

Boulder, CO 80301 USA

Business Hours

Weekdays: 9am to 5pm

Weekends: CLOSED

© 2024 Scaled Agile, Inc.

Get News
Terms of Use
Privacy Policy
Code of Conduct
Remote Training Policy

https://scaledagileframework.com/pi-planning/ 11/11