A records-retention team recodes production defects as new feature stories so velocity stays pretty. What should the SM/TC do?
Select an answer to reveal the explanation.
Short Explanation
Relabeling a leak as a new fountain does not dry the basement. If retention bugs become "features," the board looks busy while the same holes keep flooding flow. Leave defects in the open so the team can stop making them.
Full Explanation
Hiding defects inside feature accounting blocks quality-driven flow improvement because the system never sees rework, escaped defects, or weak Done. The SM/TC should keep defects visible so the records-retention team can inspect causes and invest in Built-in Quality rather than cosmetic velocity. Continuing the relabel, freezing new work to defend an inflated number, or outsourcing the count to Finance all protect the scoreboard instead of the workflow. Transparent quality work is what lets flow time drop.