A low-stakes UI color dispute on the parks reservation site is scheduled as a full-day offsite. How should the Scrum Master / Team Coach match strategy to the conflict?
Select an answer to reveal the explanation.
Short Explanation
A button color is not a constitutional convention. A full-day offsite for parks UI trivia burns the room’s patience for the next real fight. Match a small strategy to a small conflict.
Full Explanation
Strategy intensity should match conflict scale. A low-stakes parks reservation UI color dispute does not need a full-day offsite, legal escalation, or a council freeze. Over-processing trivia trains the ART to treat every disagreement as a crisis and wastes facilitation capacity needed for real resident-impact fights. The Scrum Master / Team Coach designs a light, proportional path after analysis—quick decision rule, Product Owner call, or short design spike—so parks delivery continues without burning the room’s patience.
Keeping the full-day offsite for trivia burns facilitation credibility for the next real fight. Escalating color to legal counsel as a values conflict misclassifies the stakes. Freezing the parks site until council votes on the palette stops public service for a palette fight.
Exam caveat: match intervention weight to stakes and intensity; bigger is not always better. Operational check: if the only resident impact is preference, use a lightweight decision path and save heavy facilitation for structural or safety conflicts.
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.