Definition of PI planning
PI planning is an event of the SAFe framework (Scaled Agile Framework). The framework’s website (framework.scaledagile.com) defines it as a fixed-cadence event for an entire Agile Release Train (ART) that aligns the teams and stakeholders on a shared mission and vision. The framework itself is presented in our entry on SAFe; this entry is limited to the event.
There, the acronym PI stands for Planning Interval: a span of 8 to 12 weeks during which the train’s teams deliver the work that meets their objectives. The website’s blog recalls that PI used to stand for “Program Increment”, the framework having since dropped the word “program”. PI planning follows this rhythm, every 8 to 12 weeks, and usually lasts 2 days.
These elements come from the public part of the website (“PI Planning” and “Planning Interval” pages, glossary, blog), consulted on 12 November 2026. The detailed agenda of the two days is reserved for signed-in users: this entry does not describe it.
What the framework expects from the event
During PI planning, the train’s teams build together a plan to deliver, over the coming PI, the work of highest value. Among the benefits the website attributes to the event are:
- face-to-face communication between team members and stakeholders;
- alignment of development with business objectives;
- identification of dependencies and collaboration between teams;
- matching demand to capacity, by removing excess work in progress;
- fast decision-making.
Participants, preparation and outputs
| Element | What the framework’s website says |
|---|---|
| Participants | All the teams of the train, stakeholders and leaders |
| Facilitation | The Release Train Engineer (RTE), who, according to the glossary, facilitates the train’s events and processes |
| Place in the calendar | The Innovation and Planning (IP) iteration, which sets aside time for planning without weighing on delivery |
| Attendance | Everyone physically together where possible; otherwise remotely, provided all members of the train take part |
| Preparation | Three dimensions: organisational readiness, content readiness and logistics |
| Outputs | PI objectives to which the teams commit, and an ART planning board |
According to the glossary, PI objectives summarise the business and technical goals that the teams and the train intend to achieve during the PI, and are split into committed and uncommitted objectives. The ART Planning Board shows feature delivery dates, dependencies between teams and milestones. The glossary also defines a Confidence Vote, which measures the teams’ and the train’s belief that they can meet these objectives.
PI planning, iteration planning and OKRs: not to be confused
Iteration planning takes place at team level: according to the glossary, its members determine how much of their backlog they commit to delivering during the coming iteration. PI planning takes place at train level and covers several iterations.
PI objectives are not OKRs. The former belong to the SAFe calendar; the latter are also practised without it.
Example: PI planning for a train of six teams
Consider six teams jointly developing a retailer’s order-taking system. Brought together for PI planning, they compare their plans. Two planned features depend on the same team, responsible for the interfaces with the warehouses, which cannot serve both during the PI.
The ART planning board makes this conflict visible: both delivery dates rest on the same dependency. One of the features is pushed back, and the team concerned moves the corresponding objective into its uncommitted objectives. The committed objectives are set on the plan thus corrected.
Choosing a framework and preparing a first joint planning session are covered on our page devoted to agile at scale; the decision to adopt SAFe, in our article on SAFe and agile project management at scale.