Multi-Team Increment Planning

Purpose

Multi-Team Increment Planning is the heartbeat event of large-scale agile frameworks. It brings all teams in a team of teams together for two days to align on a shared vision, identify cross-team dependencies, and commit to increment objectives.

At a glance

How to run

Day 1:

1. Business context (60 min) — Senior leadership presents the strategic themes and vision.
2. Product/solution vision (60 min) — Product Management presents the top features for the increment.
3. Architecture vision (30 min) — System Architect presents enablers and architectural runway.
4. Team breakouts (180 min) — Each team drafts iteration plans, identifies risks, and maps dependencies.
5. Draft plan review (60 min) — Teams present their draft plans. Other teams flag dependency conflicts.
6. Management review (30 min) — Adjust scope and resolve conflicts.

Day 2:

1. Planning adjustments (60 min) — Teams refine plans based on Day 1 feedback.
2. Final plan review (90 min) — Each team presents final increment objectives.
3. Program risks (60 min) — ROAM exercise: Resolved, Owned, Accepted, Mitigated.
4. Confidence vote (15 min) — Fist-of-five across the entire team of teams. Below 3 triggers re-planning.
5. Increment planning retrospective (30 min) — Improve the event itself.

Materials needed

• Program board (physical or digital) showing features, teams, iterations, and dependencies
• Feature descriptions from Product Management
• Architectural runway documentation
• Dependency and risk boards
• Fist-of-five cards for confidence vote

Pitfalls & common mistakes

• Skipping the confidence vote — Without it, commitment is hollow.
• Business context is missing — Without strategic framing, teams plan in a vacuum.
• Dependencies not visualized — Use a physical or digital program board with string/lines.
• Over-loading the increment — Leave capacity buffer (typically 20%) for unplanned work.
• Remote teams are second-class — Invest in equal tooling and facilitation for distributed participants.

Inclusion & accessibility

• Provide agendas and feature descriptions at least one week in advance.
• Assign a remote facilitator for distributed teams.
• Use multiple time zones fairly — rotate start times if needed.
• Captioning and translation for multilingual teams of teams.

Variations

• Distributed increment planning — All-remote with Miro or Mural, video breakout rooms, and digital program board.
• 3-day increment planning — For very large teams of teams (10+ teams), add a half-day for deeper dependency resolution.
• Increment planning lite — For smaller teams of teams (2–3 teams), condense to one day.

When NOT to use this

• If you have a single team — Sprint Planning is sufficient.
• If the organisation does not have a genuine need for cross-team alignment — the event becomes expensive overhead.

Source & further reading

• Leffingwell, D. (2020). *SAFe Reference Guide*. Scaled Agile Press.
• Knaster, R. & Leffingwell, D. (2020). *SAFe Distilled*. Addison-Wesley.