What does a program board help teams identify?

The correct answer is B. Dependencies between teams. A program board (used in SAFe and similar scaled Agile frameworks) is specifically designed to visualize cross-team dependencies - the connections between teams' work that must be coordinated to deliver program-level features. Without a program board, these dependencies remain…

PI Planning

Question

Options

AProgram-level risks
BDependencies between teams
CEach teams tasks
DWork breakdowns

How the community answered

(24 responses)

A
8% (2)
B
88% (21)
C
4% (1)

Explanation

A program board (used in SAFe and similar scaled Agile frameworks) is specifically designed to visualize cross-team dependencies - the connections between teams' work that must be coordinated to deliver program-level features. Without a program board, these dependencies remain hidden and become blockers during execution.

A (Program-level risks) is wrong because risks are tracked in a risk register or ROAM board, not the program board itself.
C (Each team's tasks) is wrong because individual team tasks live on each team's own iteration board or backlog, not the program board.
D (Work breakdowns) is wrong because decomposing work into tasks happens during team-level planning, not at the program board level.

Memory tip: Think of the program board as a web connecting teams - its whole purpose is to show the threads (dependencies) between them, not what's happening inside any single team.

Topics

#program board#PI Planning#team dependencies#coordination

Community Discussion

No community discussion yet for this question.

Full SAFE-SP Practice