PI Planning Board Template

PI Planning Board: [Train name], PI [number]

A record of a planning interval (PI) planning event for a team of agile teams that plan and deliver together: the context and features going in, each team's capacity and objectives with business value, the board of features, milestones and cross-team dependencies by iteration, the risks sorted with the ROAM convention, the confidence vote, and, at the end of the interval, the results against plan. PI planning is best known from the Scaled Agile Framework (SAFe), where it is a recurring, typically two-day event for an Agile Release Train every 8 to 12 weeks. This page is a generic, original format and does not reproduce SAFe material. Replace every [bracketed] value and every row marked Example.

Document control

Approvals

Revision history

The worked example is the Claims Digital train of the fictional Fernhallow Insurance Group: four teams (Atlas, Beacon, Cobalt, Delta) planning PI 27.2, from 2027-04-05 to 2027-06-11: four two-week iterations and a two-week innovation and planning iteration.

1. Context and features

Milestones and fixed dates: [regulatory dates, releases, events].

Example: Marketing campaign for online claims starts 2027-06-01.

2. Team capacity

3. Team objectives

3.1 Team [name]

Example: Team Atlas planned business value for committed objectives is 25 (10 + 8 + 7).

4. Train board

5. Risks (ROAM)

6. Confidence vote and commitment

Commitment statement: [The teams commit to the committed objectives in section 3 under the stated risks and dependencies.]

7. Results at the end of the interval

Example: Atlas scored 10 on OBJ-A1, 6 on OBJ-A2 (scan service late, DEP-02), 7 on OBJ-A3 and 0 on OBJ-A4. Cobalt exceeded plan because it completed an uncommitted objective. Delta's shortfall goes to the train retrospective.

8. Related templates

• Release plan and Roadmap
• Prioritization (WSJF and others)
• Sprint planning for each iteration
• Sprint retrospective
• RAID log for risks that outlive the interval
• Team charter

Glossary

• Planning interval (PI): a fixed timebox of several iterations in which a team of teams plans and delivers together. SAFe 6.0 uses this name; earlier SAFe versions called it a program increment.
• Train: a long-lived team of agile teams that plans, commits and delivers together; in SAFe, an Agile Release Train (ART).
• Innovation and planning (IP) iteration: a final iteration in the interval kept for innovation, learning and the next planning event.
• Business value (BV): a relative score that business owners give an objective.
• ROAM: a convention for sorting risks as Resolved, Owned, Accepted or Mitigated.
• FNOL: first notice of loss, the first report of an insurance claim.

Standard and licence note

Structure aligned with PI planning as described in the Scaled Agile Framework (SAFe 6.0, Scaled Agile, Inc.), PI planning article updated 15 March 2026: https://framework.scaledagile.com/pi-planning. SAFe is cited by name only: no SAFe text, figures or graphics are reproduced, and the sections, wording, ROAM and predictability descriptions and the fictional Fernhallow example are original. Official text: Scaled Agile, Inc., licensed access and permissions: https://framework.scaledagile.com/usage-and-permissions. Scaled Agile Framework and SAFe are registered trademarks of Scaled Agile, Inc. Check the current SAFe guidance before use. Template licence: MIT.