Free PI Planning Board — A Program Board That Actually Calculates

Map teams, iterations, features and cross-team dependencies for your next program increment. Unlike a whiteboard template, this board warns you live when a dependency points backwards or a team is planned over capacity. Free, no sign-up — everything runs in your browser.

Iteration 1
Iteration 2
Iteration 3
Iteration 4
IP
8/20
13/20
5/20
21/20
8/20
5/16
8/16
13/16
dependencycross-teamsame iterationbackwards
“Checkout screen” depends on “Stripe integration” but is scheduled 1 iteration earlier.
Payments is at 105% capacity in iteration 3 (21 of 20 pts).

How the PI planning board works

The same program board you'd build on a wall — except it does the math your sticky notes can't.

1. Set up teams and capacity

Add a row per team and give each one an honest points-per-iteration capacity — after support rotations, holidays, and the specialist who's half-lent elsewhere. Pick how many iterations your PI runs; the IP iteration is kept as a buffer.

2. Place features, draw dependencies

Add feature cards to team × iteration cells with a point estimate, then link the cards that depend on each other. Capacity bars fill as you plan, and any dependency that points backwards in time turns red immediately.

3. Resolve conflicts, then make it real

Drag cards between iterations until the warnings go green — that's your PI plan, agreed before the increment starts. Save it to Axioplan and it opens as a live Gantt with swimlanes, dates and every dependency intact.

Why not just use a whiteboard template?

Miro, Mural and FigJam templates give you the picture of a program board. They don't give you the two checks the board exists for — dependency order and team capacity. Those live in the math, not the drawing. Our guide to what PI planning is covers the full event; this tool covers the part where plans succeed or fail.

Backwards dependencies surface on day one

The most expensive PI planning failure is a feature scheduled before the thing it depends on — usually discovered mid-increment as a surprise blocker. On a sticky-note board that's an invisible mistake; here the string turns red the moment it happens.

Capacity math you can't accidentally skip

SAFe's own guidance says never plan to 100% capacity. A template can't enforce that; this board shows a load bar per team per iteration that goes amber at 80% and red when a team is over-planned, so the conversation happens in the room.

A board that outlives planning day

Whiteboard program boards go stale by week two because updating string is manual labor. Save this board to Axioplan and it becomes a live Gantt — when a feature slips an iteration, the dependencies and dates move with it.

Frequently asked questions

Common questions about the PI planning board and program boards in general.

After planning day

Keep the program board alive for the whole increment

The board on the wall is a photo by week two. Save yours to Axioplan and it stays a working plan.

From iterations to real dates

Your board becomes a Gantt chart: teams as epic swimlanes, features as scheduled tasks, iterations as actual two-week slots on a calendar.

Dependencies that stay alive

Every string you drew comes across as a task dependency. When a feature slips, the plan shows exactly what it drags with it — all increment long, not just on planning day.

Capacity with real people

Replace points-per-iteration with actual team members, roles and allocation, so the next PI is planned against availability instead of headcount.