Stormwater models accumulate hacks because the team says there is no time to refactor, and each new change takes longer. How should the Scrum Master/Team Coach treat refactoring?
Select an answer to reveal the explanation.
Short Explanation
Stormwater code full of hacks is a culvert packed with debris: every new storm moves slower. Refactoring is clearing the pipe, not hanging a pretty sign after the flood. Budget it as quality that keeps flow moving.
Full Explanation
Refactoring is a built-in quality practice that protects future flow. Deferred cleanup on stormwater models increases the cost of every later change and eventually stalls the team. Waiting for PI slack, a capital project, or a perfect codebase before visualizing work treats refactoring as optional polish. The Scrum Master/Team Coach should help the team include refactoring in the flow of work.