Mid-Sprint, middle managers pull Developers off the transit-app team for “higher-priority projects,” wrecking the Sprint Goal and the release forecast. What should the Product Owner escalate?
Select an answer to reveal the explanation.
Short Explanation
You cannot forecast a bus route if the driver keeps getting pulled to drive a parade. Mid-Sprint yanking is an org-design problem, not a motivation problem. Escalate the WIP and protect the team’s focus, or every forecast is fiction.
Full Explanation
Structures that reassign people mid-Sprint destroy Focus, invalidate forecasts, and treat the Sprint Goal as optional. The Product Owner should escalate that as a systemic WIP and design issue, seeking leadership agreement that team membership is stable for the Sprint. Heroic overtime or constantly rewriting the Sprint Goal hides the structural problem. Civic products need reliable empiricism, which requires protected focus.