The 911-radio-upgrade team copies the ART program board and uses it as their only team board. What distinction should the SM/TC draw?
Select an answer to reveal the explanation.
Short Explanation
The program board is the highway map; the team board is the shop floor. Copying ART dependencies does not show how a radio story actually moves. 911 still needs its own workflow visualization.
Full Explanation
Team Kanban visualizes the team's own workflow; it is not a copy of the ART program board. The program board is the highway map; the team board is the shop floor. Copying ART dependencies does not show how a radar permit, work order, or story actually moves through local states, waits, and policies.
Claiming the program board is sufficient because team workflow is just a smaller ART fails because altitude and purpose differ. Saying team boards are optional once Features appear on the program board fails because Features on the program board do not expose team-level wait states. Copying the program board and adding a swimlane per person fails because it mixes ART dependency views with people-centric anti-patterns.
Exam caveat: both boards matter; neither replaces the other. Operational check: keep the ART program board for cross-team dependencies, maintain a team board of real local states, avoid copying ART columns wholesale, and ensure daily pull uses the team board while PI planning uses both views appropriately. Keeping team and program boards distinct prevents altitude confusion during PI Planning and daily pull alike. Keeping team and program boards distinct prevents altitude confusion during PI Planning and daily pull alike.