A legacy change-advisory board must approve every 311-text tweak, so small civic-app copy changes sit for weeks. What should the Scrum Master/Team Coach do?
Select an answer to reveal the explanation.
Short Explanation
A CAB that signs every 311 comma is a brick on the firehose. Low-risk copy should not wait like a data-center cutover. Change the policy with a risk lens, do not sneak around it or write longer permission essays.
Full Explanation
Remediating legacy policies is a flow accelerator: a change-advisory board on every 311-text tweak is a structural interrupt, not a required safety control for low-risk copy. The Scrum Master/Team Coach should coach a risk-based exception so small text can flow while higher-risk changes keep review. Shadow routes and unchanged policy leave the delay in place. Mentioning the wait at Inspect and Adapt without changing the rule is not remediation.