Permit plan-check and fire-sprinkler-review teams only "collaborate" in a 90-minute weekly status call. What should the Scrum Master / Team Coach promote instead?

Cross-team collaboration means doing work together—joint refinement, shared examples, and early integration—not expanding status theater. When permit plan-check and fire-sprinkler-review teams only "collaborate" in a 90-minute weekly status call, the Scrum Master / Team Coach should promote joint working collaboration with shared examples and refinement rather than a longer status meeting. Applicants and life-safety reviewers need synchronized understanding of requirements, not longer read-alouds.

Extending the call to three hours so every ticket can be read aloud fails by concept: more status time is still status, not joint problem-solving. Replacing both teams with a single status analyst who reports to the Release Train Engineer fails by concept by removing the people who hold domain knowledge from collaboration. Canceling all contact so each team maximizes local velocity fails by concept: local speed without integration creates late fire-life-safety conflicts on permits.

Exam caveat: SASM and SAFe collaboration guidance favor working together on shared work items over status reporting; longer meetings are a common false fix. A short coordination sync can remain—pairing it with joint refinement and shared acceptance examples is what actually reduces cross-team defects.

Operational check: schedule joint refinement on overlapping permit stories, share concrete plan-check and sprinkler examples, integrate earlier than System Demo, shorten pure status time, and verify dependency surprises and rework drop compared with the weekly status-only pattern.