The benefits portal team skips automated tests to go faster and then drowns in production patches. What should the Scrum Master/Team Coach link to flow?
Select an answer to reveal the explanation.
Short Explanation
Skipping tests to go faster is like skipping the inspection sticker to get the bus out of the yard. It rolls, then it lives in the shop. Test-first and CI are how the benefits portal stays on the road instead of drowning in patches.
Full Explanation
Built-in quality is a flow practice, not ceremony. Skipping automated tests on a benefits portal increases production patches, which consume capacity and stretch flow time. Test-first work and continuous integration catch defects while they are cheap. Product Owner risk acceptance, patch-as-Done, and documentation freezes do not restore flow; they either license rework or stop value entirely.