The immunization-registry team has no Definition of Done, so stories marked done fail System Demo and stall the ART. What should the Scrum Master/Team Coach coach?
Select an answer to reveal the explanation.
Short Explanation
If done means something different on every immunization story, System Demo is where the argument starts. Write the Definition of Done down. That is how quality stops being a surprise that stalls the train.
Full Explanation
An explicit Definition of Done makes quality visible and reduces downstream ART stalls. Without DoD, the immunization-registry team marks stories done that then fail System Demo, blocking ART flow and public-health demo confidence. The Scrum Master/Team Coach should coach a clear, shared DoD so “done” means demo-ready quality, not a local declaration.
Keeping implicit done and adding a demo-repair sprint after every PI fails by concept: it schedules chronic rework instead of preventing it. Letting each developer define done privately fails by concept because autonomy without a shared quality bar creates inconsistent increments. Counting any merged commit as done regardless of demo readiness fails by concept by equating code movement with a working civic registry increment.
Exam caveat: SAFe requires teams to define and apply Done so ART-level integration and System Demo can succeed; missing DoD is a flow and quality defect, not a documentation nicety. DoD should include integration and quality expectations appropriate to immunization-registry risk.
Operational check: facilitate a written team DoD covering tests, integration, and demo readiness; apply it at Iteration Review; measure System Demo failures attributable to incomplete done; and refine the DoD until downstream stalls drop.