A code-enforcement director wants to replace all team events with a single weekly steering meeting. How should the Scrum Master / Team Coach respond?
Select an answer to reveal the explanation.
Short Explanation
A weekly steering meeting is a city council status hour, not a team inspect-and-adapt loop. Planning, review, and retro each have a job steering cannot do. Keep the lightweight events that produce those outcomes.
Full Explanation
Lightweight team events that serve inspect-and-adapt outcomes should not be replaced by a single weekly steering meeting. A code-enforcement director’s efficiency argument collapses planning, sync, review, and improvement into status hierarchy. The Scrum Master / Team Coach defends the team cadence that produces working increments and experiments for neighborhood enforcement outcomes. Steering can inform; it cannot substitute empiricism.
Agreeing that one steering meeting is more efficient trades visibility for control and loses team inspection. Keeping only steering and sending minutes to the RTE as the “increment” confuses reporting with delivery. Moving planning and review into the director’s private calendar removes transparency.
Exam caveat: leadership forums complement team events; they do not replace them. Operational check: map which inspect-and-adapt outcomes disappear if code-enforcement team events die—then defend those events.
In municipal ARTs, residents experience these coaching choices as faster or slower public services—licensing lines, housing decisions, water bills, snow routes, and emergency response—so keep events and buffers tied to inspect-and-adapt outcomes. Record the decision, the owner, and the next inspection date so the team can verify civic impact.