Flow time on vital-records requests improved, but production defects spiked. How should the Scrum Master / Team Coach assess the team?
Select an answer to reveal the explanation.
Short Explanation
A birth certificate that arrives tomorrow with the wrong name is not better service. Speed without quality is just a faster mistake. Score vital-records work on both the wait and whether the record is right.
Full Explanation
When flow time on vital-records requests improves but production defects spike, the Scrum Master / Team Coach must read flow and quality together; faster certificates that are wrong are not a performance win. Municipal vital records demand correctness because errors cascade into identity, benefits, and legal harm for residents. Declaring the team high performing because faster flow is the only score that matters ignores defect harm and teaches cutting corners. Ignoring defects until the next annual audit keeps the flow chart clean while residents live with errors for months. Rewarding a utilization bonus for shorter cycle time pays for speed that may have removed necessary checks. Exam caveat: SASM performance assessment balances flow and built-in quality; flow-only scores are incomplete on advanced team-coach items. Operational check: pair the flow metric with defect rate or reopen rate for vital-records certificates, facilitate a root-cause look at what was sacrificed for speed, restore quality checks in the Definition of Done, and re-measure both flow and quality after one or two iterations. Present both measures to leadership so civic "faster" is not mistaken for "better," and confirm operators still trust the certificates leaving the team.