The 911 CAD team and the RMS team discover a blocking dependency at System Demo. What should the Scrum Master / Team Coach push for next time?
Select an answer to reveal the explanation.
Short Explanation
Finding a CAD-to-RMS dependency at System Demo is finding the missing hydrant after the fire. Coaches push that conversation into earlier refinement and a visible plan. Surprise at demo is a collaboration failure, not a feature.
Full Explanation
Cross-team dependencies should be visible during planning and refinement so teams can sequence, spike, or restory before a demo surprise. Waiting for System Demo, hiding the issue until Inspect and Adapt, or converting both backlogs into a coach-owned WBS does not improve collaboration. At team-coach depth, the Scrum Master / Team Coach arranges earlier joint refinement and program-board-style visibility without taking the RTE's train-facilitation job. Early sight is the skill.