Program board
The program board is the visual artefact produced during PI Planning: a grid of iterations × teams showing which features each team is committing to in which iteration, with explicit dependency lines drawn between cross-team dependencies and milestones (releases, demos, external events) called out.
The program board makes cross-team dependencies visible early — at PI Planning, not at PI mid-point when the dependency is missed. Healthy program boards have few red dependency lines (most work is independent), explicit owner-and-receiver names on each dependency (not 'platform team will help'), and visible milestone markers. Bad program boards either have a spider's web of dependencies (the ARTs are sliced wrong) or no dependencies at all (the teams aren't being honest about coupling). The board is a working artefact during the PI: every iteration, the RTE walks the board and surfaces dependency status, schedule slips, and risk movement.
Related terms
- PI planning
PI Planning is the 1-2 day event at the start of each Program Increment where the entire Agile Release Train — all teams, Product Management, Business Owners, System Architect — assembles to plan the upcoming PI.
- Program increment (PI)
A Program Increment is SAFe's timebox for an Agile Release Train — typically 8-12 weeks, usually 5 iterations of 2 weeks each.
- Risk ROAMing
ROAM is the SAFe protocol for handling risks identified during PI Planning: each risk is categorised Resolved (already handled), Owned (someone now owns the mitigation), Accepted (the team accepts the risk as-is), or Mitigated (a specific reduction action is added to the plan).