Program Increment Cadence

The org's execution rhythm — how every team's sprints stay in sync once the plan is set.

Try It

Plan sets the direction and the budget (OKRs, Strategic Planning, Annual Operating Plan). Reflect checks it against reality (MBR & QBR). This is what runs in between: the actual cadence of work, synchronized across every team on the plan at once — not any single team's own sprint mechanics, which is Team's own Agile / Delivery Process. The standard framework for that synchronization layer is the Scaled Agile Framework (SAFe), run by Agile Release Trains and a small set of standing Roles & Responsibilities.

The Program Increment Cadence

A repeating cycle, typically 8–12 weeks long, that every team on the train moves through together:

1

PI Planning — every team on the train plans the next Program Increment together, against the same backlog, in the same room or call — not separately.

2

Iterations — each team runs its own short sprints inside the Program Increment, executing against the plan they just set together.

3

System Demo — every iteration, the train demos the integrated work across all teams, not just one team's slice, so integration problems surface early.

4

Inspect & Adapt — at the close of the Program Increment, the whole train stops to look at quality and flow together and adjusts before the next PI Planning.

Mind the Gap

Run PIs on a quarterly cadence and the math doesn't land evenly: six two-week sprints fill 12 weeks, leaving a few spare weeks across the year that don't belong to any sprint. A common pattern is a dedicated gap week between PIs — SAFe calls this an Innovation and Planning (IP) Iteration — used to lock the next PI, secure cross-team dependencies, and refine backlogs before PI Planning starts. It also doubles as a great week for team building, hackathons, learning and development, or a bug bash — work that never fits inside a committed sprint but still needs to happen somewhere.

See the Annual Calendar for this cadence laid out across a real year — sprint by sprint, alongside the budget cycle's OP1/OP2 and the people calendar's review and comp-planning milestones.

Try It

Paste this into ChatGPT, Claude, or whatever AI tool you use:

Help me design a Program Increment cadence for my organization. Ask me how many teams are on the train, then walk me through setting PI length, the shape of PI Planning, how often we'll run System Demos, and what Inspect & Adapt should actually cover at the end of each PI.