Back to Glossary
Agile
PI Planning
Quick Definition
A cadence-based, face-to-face or virtual event in which all members of an Agile Release Train plan the next Planning Interval (PI) together. Older SAFe versions called the PI a Program Increment.
Detailed Explanation
In SAFe, PI Planning typically lasts two days and happens at the start of each Planning Interval (called a Program Increment before SAFe 6.0). Participants are the teams, product management, system architects, the Release Train Engineer, business owners and other stakeholders. Inputs include the vision, the prioritised backlog and architectural guidance. Outputs include team plans with PI objectives, an ART planning board of dependencies (formerly the program board), a risk list and a confidence vote.
Example: A release train of eight teams meets to plan the next increment. Each team drafts iteration plans and objectives, dependencies are marked on the ART planning board and the group votes on confidence in the plan.
How it differs from related terms: Sprint planning plans one team's iteration. PI Planning plans a multi-iteration Planning Interval across many teams. For the full agenda, roles and common mistakes, see the CertScope blog guide "PI Planning in SAFe".
Related Terms
Relevant Frameworks
SAFe