Demo feedback on the open-data team is never put on the backlog. What should the Scrum Master / Team Coach close?
Select an answer to reveal the explanation.
Short Explanation
Cheering an open-data demo and then losing the comments is applause with no encore list. If feedback never hits the backlog, the review had no outcome. Write it down where the next plan can see it.
Full Explanation
Demo feedback must change future work. When open-data review comments never reach the backlog, inspection is theater. The Scrum Master / Team Coach closes the loop by putting feedback on the backlog or plan so stakeholders see their input affect public datasets and portals. Archived slide comments are not empiricism.
Archiving comments in a deck to mark the event complete hides action. Asking stakeholders to email the director instead of the Product Owner breaks backlog ownership. Waiting until next PI Planning to mention feedback delays learning across iterations.
Exam caveat: Iteration Review without backlog follow-through fails the event’s purpose. Operational check: before closing an open-data review, capture each accepted feedback item on the backlog with an owner.
In municipal ARTs, residents experience these coaching choices as faster or slower public services—licensing lines, housing decisions, water bills, snow routes, and emergency response—so keep events and buffers tied to inspect-and-adapt outcomes. Record the decision, the owner, and the next inspection date so the team can verify civic impact. Confirm the next demo or metrics review will show whether the change helped residents.