Team sync on the tax-assessment crew has become a 45-minute status report to the coach. How should the Scrum Master / Team Coach redirect the event?
Select an answer to reveal the explanation.
Short Explanation
A 45-minute status to the coach is a roll call, not a team sync. Tax assessment still has an iteration outcome and real blockers. Point the room at those—not at briefing the facilitator.
Full Explanation
Team sync is for coordination toward the iteration or PI outcome and for impediment removal, not a 45-minute status report to the coach. On a tax-assessment crew, assessors should sync dependencies, risks, and help needed so valuation work flows. The Scrum Master / Team Coach redirects the event away from reporting upward and toward team-to-team clarity. Status theater steals time from assessment accuracy and cycle time.
Lengthening the sync to 90 minutes doubles the anti-pattern. Having the coach collect status for a council dashboard turns the meeting into a management briefing. Replacing the sync with a written status email to the Scrum Master removes live coordination entirely.
Exam caveat: the coach facilitates; the team owns the conversation about progress and blockers. Operational check: if sync answers are aimed at the coach, ask “who needs what from whom to move assessments?” and stop the report-out format.
In municipal ARTs, residents experience conflict outcomes as delayed permits, missed benefits, unsafe shelter conditions, or opaque public data—so the Scrum Master / Team Coach keeps facilitation tied to service flow, safety, and transparent inspection rather than positional wins. Document the chosen frame or strategy, the evidence used, and the next check date so the team can see whether the intervention improved civic delivery.