After a joint demo of the business-license plus payments slice, neither team records follow-ups. What should the Scrum Master / Team Coach want?
Select an answer to reveal the explanation.
Short Explanation
A joint demo with no next actions is a ribbon cutting that forgets who has the keys. License and payments just learned something together—write who does what next. Otherwise the applause is the only deliverable.
Full Explanation
After a joint demo of a business-license plus payments slice, the Scrum Master / Team Coach should want explicit next collaboration actions owned by the teams before the demo dissolves. Feedback without owners becomes nostalgia; municipal license and payment follow-ups need named next steps, timing, and team ownership. A photo of the demo slide as the only record optimizes for ending on time and loses actionable learning. The coach privately remembering feedback and assigning it later by email recreates the coach as backlog secretary and hides ownership from the teams. Waiting until Inspect and Adapt to mention anything heard in the demo stretches the feedback loop across the PI and risks losing urgency on resident-facing payment defects. Exam caveat: SASM ties demos and collaboration to actionable follow-up; photos, coach memory, and I&A-only capture are weak substitutes for immediate owned actions. Operational check: before closing the joint demo, list feedback items, assign owning team and next date for each collaboration action, place them on the relevant boards, and verify within one iteration that at least the highest-priority follow-up moved. Keep the coach facilitating capture, not privately absorbing the work.