Closed yes-or-no questions such as "Did you update Jira?" dominate the public-housing-maintenance team's sync. What should the Scrum Master / Team Coach shift toward?
Select an answer to reveal the explanation.
Short Explanation
"Did you update Jira?" is a metal-detector question—it beeps, then everyone moves on. Housing-maintenance syncs should ask whether units are actually becoming livable. Open questions about outcomes beat a roll call of checkboxes.
Full Explanation
Open questions about progress toward resident outcomes beat closed tool-status pings. Dominating the public-housing-maintenance sync with “Did you update Jira?” trains yes-or-no theater instead of conversation about work that keeps units livable for residents. The Scrum Master/Team Coach should shift toward open questions on impediments, flow, and resident impact while keeping the timebox.
Adding more closed questions so every ticket status is captured in under a minute fails by concept: faster interrogation still misses substance that matters for housing maintenance. A written Jira audit after the sync fails by concept by moving tool policing outside collaboration without improving outcomes. Individual performance scoring based on who answered yes first fails by concept because it gamifies compliance, not maintenance value for residents.
Exam caveat: Daily sync coaching favors meaningful progress and impediment dialogue; tool hygiene can be lightweight automation or a quick board glance, not the sync’s primary purpose. Open questions still stay timeboxed—open does not mean endless discussion for housing-maintenance teams.
Operational check: replace most closed tool questions with open prompts about progress and blockers toward resident outcomes, keep Jira updates as a side discipline, and observe richer impediment surfacing within the existing timebox.