The immunization-registry iteration review is a slide deck of “we were busy.” What should the Scrum Master / Team Coach require of the event?
Select an answer to reveal the explanation.
Short Explanation
“We were busy” is a timesheet, not a review. Immunization-registry users need to see the increment against the goal and say what is missing. Show the work; do not narrate the hustle.
Full Explanation
Iteration Review inspects working software or service against the iteration goal and captures feedback. An immunization-registry review that is only a “we were busy” slide deck fails that purpose. The Scrum Master / Team Coach requires a real increment clinicians can react to—screens, workflows, data quality—so feedback improves public-health delivery. Effort narratives are not increments.
Accepting the busy-slide because effort proves progress confuses activity with outcomes for clinicians. Canceling the review to avoid bothering clinicians removes the feedback loop those clinicians need. Reading utilization hours aloud as the review outcome measures the wrong thing.
Exam caveat: demo working results; busy metrics are not a substitute for inspection. Operational check: if the registry review has no working increment, stop the slides and show the smallest runnable service slice instead.
In municipal ARTs, residents experience conflict outcomes as delayed permits, missed benefits, unsafe shelter conditions, or opaque public data—so the Scrum Master / Team Coach keeps facilitation tied to service flow, safety, and transparent inspection rather than positional wins. Document the chosen frame or strategy, the evidence used, and the next check date so the team can see whether the intervention improved civic delivery.