Fire RMS and EMS ePCR teams collide every handoff because nobody owns the interface APIs. What source of conflict should the Scrum Master / Team Coach name?
Select an answer to reveal the explanation.
Short Explanation
If two city radios sit on different frequencies and nobody owns the patch, the crews will collide at the scene. Missing API ownership is the same thing. That is an interface and role-clarity source, not "EMS is difficult."
Full Explanation
When Fire RMS and EMS ePCR teams collide every handoff because nobody owns the interface APIs, the Scrum Master / Team Coach should name unclear ownership and interfaces between teams—a role-clarity source, not a temperament problem. Missing interface ownership produces recurring handoff conflict regardless of how cooperative people intend to be in emergency response. Blaming EMS staff who simply refuse to cooperate with fire personalizes a design gap and damages trust between services. Casting it as a values clash about whether emergency services should share data may be philosophically interesting but skips the ownership vacuum that blocks daily care. Claiming it is an RTE-only problem and that team coaches must not name missing API ownership abandons SASM facilitation of cross-team clarity. Exam caveat: SASM conflict sources include unclear roles and interfaces; temperament narratives and "coaches may not name ownership" are wrong. Operational check: facilitate an ownership map for the handoff APIs, name accountable teams and contract tests, place interface work on a backlog with capacity, and verify the next incident handoff no longer stalls on "whose API." Revisit ownership in Coach Sync if collisions recur after the first fix.