In 30 seconds
- Every team on the train plans together, usually over two days.
- Outputs: team PI objectives and a board of features and dependencies.
- Ends with a confidence vote and a final plan.
What it is
In the Scaled Agile Framework, a Program Increment (PI) is a planning cycle of typically 8 to 12 weeks. PI Planning kicks it off: all teams on the Agile Release Train, plus business owners, plan together in one room or one virtual space.
A two-day agenda
Day 1: business context and vision, team breakouts to draft plans, draft plan review, management review of problems.
Day 2: planning adjustments, final team breakouts, risk review, confidence vote, retrospective.
Outputs
- Team PI objectives, rated for business value by business owners
- A program board showing feature delivery dates and cross-team dependencies
- Risks sorted as resolved, owned, accepted or mitigated
- A team confidence vote, often by fist of five
Myth vs reality
Myth · PI Planning produces a fixed 12-week plan.
Reality · Teams commit to objectives; plans adapt during the PI.
Myth · Remote PI Planning can't work.
Reality · Many trains run it virtually with good preparation.
Myth · Only leaders need to attend.
Reality · The whole train plans; that's the point.
FAQ
How long is PI Planning?
Usually two days.
What happens if confidence is low?
Teams replan until the train reaches acceptable confidence.
Is PI Planning only for SAFe?
The name is SAFe's; big-room planning exists elsewhere too.