All templates

PI Planning Template

Agile / Scrum 480 min Quarterly (per program increment) All teams in the program, product management, and leadership (20-100+ people)

The PI planning template structures a large, cross-team planning event where every team in a program aligns on a shared plan for the next increment. This is big-room planning: many teams in one place, or one virtual room, building a coordinated forecast for the weeks ahead. The output is a set of team objectives, a dependency map, and a shared commitment.

When to use it

Use it when a program of several teams needs to plan a multi-sprint increment together, typically once a quarter. It is a significant investment, often a day or two, so it suits programs where cross-team alignment is the bottleneck. This pattern comes from scaled agile frameworks, which are independent of OrgTP.

Who attends

Everyone who plans the increment attends: all teams, product management, architects, and leadership. The breadth is intentional. Decisions and dependencies get resolved in the room because the right people are present.

How to run it

Open with business context and vision so teams understand the why. Brief the room on architecture direction and planning rules. Then give teams a long breakout block to draft iteration plans and objectives against their capacity. Bring everyone back to review draft plans, surface dependencies, and name risks. Work the risks openly, deciding to resolve, own, accept, or mitigate each. Close with finalized objectives, a confidence vote, and a shared commitment.

Facilitator tips

  • Prepare relentlessly since a big event with no prep wastes everyone's time.
  • Make dependencies visible on a shared board the whole room can see.
  • Run an honest confidence vote and address low votes before committing.
  • Timebox breakouts hard so the plenary reviews stay on schedule.

Common mistakes

  • Skipping preparation, so the event becomes chaotic and unproductive.
  • Hiding dependencies until they become delivery blockers.
  • Forcing commitment despite a low confidence vote.
  • Treating it as a status meeting rather than a planning event.

Aligning a whole program? Run it in OrgTP to keep objectives, dependencies, and risks in one shared plan.

Agenda

480 minutes total · 6 sections

  1. Business context and vision 60 min
    Leadership shares the business context, product vision, and priorities for the increment.
  2. Architecture and planning briefing 30 min
    Architecture and process leads outline technical direction, standards, and planning ground rules.
  3. Team breakout planning 180 min
    Each team drafts iteration plans and objectives for the increment based on capacity and priorities.
  4. Draft plan review 60 min
    Teams present draft plans, surface cross-team dependencies, and flag risks for the group.
  5. Manage risks (ROAM) 60 min
    Review program risks and resolve, own, accept, or mitigate each one openly with the room.
  6. Confidence vote and commit 30 min
    Teams finalize objectives, take a confidence vote, and commit to the increment plan.

Run this meeting live in OrgTP

Stop copying agendas into a doc every week. OrgTP runs your meetings live — scorecard, rocks, issues, and to-dos all in one place, with your AI agents in the room.