Teams on the city housing-voucher ART each call stories done against different bars and skip a shared Definition of Done. What basic Agile quality practice should the RTE reinforce?
Select an answer to reveal the explanation.
Short Explanation
If every voucher team has a different meaning of done, the city is comparing apples to unprocessed applications. A shared Definition of Done is the common finish line so an increment is actually usable, not just coded. Without it, quality is a rumor.
Full Explanation
A shared Definition of Done establishes a common quality bar so increments called complete actually meet the same standard across teams. When city housing-voucher ART teams each call stories done against different bars and skip a shared DoD, the RTE should reinforce establishing that shared definition. Letting each team keep a private done list so Product Management never compares increments guarantees inconsistent resident-facing quality. Treating done as whatever the vendor already billed on this month's statement of work substitutes procurement for quality. Waiting until Inspect and Adapt to invent a DoD that applies only next fiscal year delays the practice when current vouchers already ship. Fleet telematics safety patches that wait for a monthly CAB still leave vehicles without fixes; improve the constraint without abandoning necessary safety review. Exam caveat: teams may add team-specific extensions, but the ART baseline DoD remains shared. Operational check: facilitate a short DoD workshop, publish the housing-voucher ART DoD, and audit a sample of done items against it in the next System Demo. Propose risk-based or more frequent review paths for standard telematics changes and measure wait time before CAB.