Program Board

What is Program Board?

A program board is a visual planning board that shows when each team will deliver features, the milestones they are working toward and the dependencies between them, usually created during PI Planning.

Updated November 2026 · 2 min read


How a program board is laid out

The board is a grid. Columns are the iterations (sprints) in the planning period; rows are the teams. Teams place cards for the features they plan to deliver in the iteration they expect to finish them. Milestones and events sit in a separate row at the top. Strings or lines connect cards that depend on each other. In recent versions of SAFe the same artifact is called the ART planning board.

ElementWhat it showsCommon convention
ColumnsIterations in the incrementUsually four or five, plus an innovation and planning iteration
RowsTeams on the trainOne row per team, plus a milestones row
Feature cardsWhen a feature is planned to be doneBlue cards
MilestonesFixed dates, releases or eventsOrange or yellow cards
DependenciesWork one team needs from anotherRed cards or red string between cards

Why it matters

A team's own plan rarely shows the risks that sit between teams. The program board makes them visible. A feature card with many strings attached is fragile: if any one of those dependencies slips, so does the feature. A string pointing backwards in time, where a team needs something before it will exist, is a planning error to fix before the event ends. The board is a simple, visual form of dependency management.

An example

During PI Planning, a retail train's program board shows a customer-loyalty feature planned for iteration 3 on the web team's row. Two red strings connect it to cards on the data team and payments team rows. One of those cards sits in iteration 4, so the dependency arrives too late. The Release Train Engineer flags it in the draft plan review, the data team pulls the work forward, and the string is redrawn to point the right way.

Keeping it useful after planning

  • Keep the board visible, physical or digital, for the whole increment
  • Review it at each ART sync or Scrum of Scrums and move cards when plans change
  • Mark dependencies that have slipped so the affected team sees them immediately
  • Use it as one input to the Inspect and Adapt retrospective

Common pitfalls

A board with dozens of red strings is a sign the teams are not organized around value; too much work depends on handoffs. That is a design problem, not a planning one, and may call for restructuring teams along value streams. Another pitfall is treating the board as a one-off poster. If it is not updated after planning, it stops reflecting reality within a sprint or two and people return to separate trackers. Risks that cannot be fixed on the board belong in the ROAM review or a RAID log.

Frequently asked questions

What is the difference between a program board and a roadmap?

A roadmap shows what will be delivered over a longer horizon, often several quarters, at a high level. A program board covers one increment of 8 to 12 weeks and shows which team will deliver which feature in which sprint, plus the dependencies between them. It is a near-term execution plan, not a strategic view.

What do the red strings on a program board mean?

Red strings, or red cards, mark dependencies: one team needs something from another before it can finish a feature. They let everyone see where plans are linked and where a delay would spread. A string that points backward in time shows a dependency that will not be ready when needed, which must be resolved.

Who owns the program board?

The Release Train Engineer usually facilitates and maintains it, but every team owns its own row and keeps its cards accurate. Product management uses the board to check that the features with the highest priority are planned early, and business owners use it to see whether committed milestones are realistic.