Agile guide · Scaling Agile
What Is PI Planning? A Guide to SAFe Program Increment Planning
PI Planning is a regular event in which every team on an Agile Release Train plans the next Program Increment together, usually over two days. It aligns dozens of people around shared objectives and exposes dependencies before they cause delays.
Key takeaways
- PI Planning aligns a whole ART on shared objectives, usually in two days.
- Outputs are PI objectives, a planning board, handled risks and a confidence vote.
- Preparation and visible dependencies make the event work.
Why PI Planning matters
- Aligns teams with business goals and each other.
- Exposes dependencies and risks early.
- Builds commitment because teams create their own plans.
- Replaces weeks of meetings and email with two focused days.
Inputs
- Business context and strategic themes.
- Product vision and the top features in the ART backlog.
- Architecture vision and enablers.
- Each team's capacity for the PI.
A typical two-day agenda
Day 1
- Business context from a senior leader.
- Product and solution vision from Product Management.
- Architecture vision and development practices.
- Planning context and logistics from the RTE.
- Team breakout 1: teams draft plans and objectives and identify risks and dependencies.
- Draft plan review with all teams.
- Management review and problem-solving to adjust scope or resources.
Day 2
- Planning adjustments from management.
- Team breakout 2: teams finalise plans and objectives.
- Final plan review; Business Owners assign business value to objectives.
- Program risks are addressed using ROAM: Resolved, Owned, Accepted or Mitigated.
- Confidence vote: each person shows confidence in the plan with one to five fingers.
- Rework if confidence is low.
- Planning retrospective.
Outputs
- Team PI objectives with business value assigned.
- ART planning board (program board) showing features, milestones and dependencies across teams.
- A list of risks and how each is handled.
- A commitment from the train, confirmed by the confidence vote.
Tips for a successful PI Planning
- Prepare a well-refined feature backlog beforehand.
- Keep the business context short and inspiring.
- Make dependencies visible with strings, arrows or digital links.
- Plan at about 80% of capacity to leave room for the unexpected.
- For remote events, split days across time zones and use a shared digital board.
Free templates for this topic
Frequently asked questions
How often does PI Planning happen?
Once per Program Increment, typically every 8 to 12 weeks.
Who attends PI Planning?
Ideally everyone on the ART, plus Business Owners and key stakeholders.
What is PI Planning in SAFe?
A regular event, usually two days, in which all teams on an Agile Release Train plan the next Program Increment together.
How long does PI Planning take?
Typically two days, though large or distributed trains sometimes spread it over more days.
What are the outputs of PI Planning?
Team PI objectives with business value, an ART planning board showing features and dependencies, a list of risks and a commitment confirmed by a confidence vote.
What is ROAM in PI Planning?
A way of handling risks: each is marked Resolved, Owned, Accepted or Mitigated.
What is the confidence vote in PI Planning?
At the end of PI Planning, each person shows confidence in the plan with one to five fingers. If confidence is low, the plan is reworked.
What is the program board in PI Planning?
A visual board, now often called the ART planning board, showing features, milestones and cross-team dependencies for the PI.
Can PI Planning be done remotely?
Yes. Many trains run it online with digital boards, video breakouts and adjusted schedules for time zones.
What should be prepared before PI Planning?
A refined feature backlog, business context, architecture vision and each team's capacity for the PI.
Who facilitates PI Planning?
The Release Train Engineer facilitates, with Product Management presenting the vision and Business Owners assigning business value.