The open-data team and the privacy office clash over publishing resident datasets. How should the Scrum Master / Team Coach timebox a strategy for this values conflict?
Select an answer to reveal the explanation.
Short Explanation
Privacy versus open data is not a button color. A same-day story fight will not settle resident rights. The coach timeboxes a longer path with principles, legal, and Product Management—still a plan, just the right size.
Full Explanation
Values and policy conflicts need longer, multi-role paths. When open-data and privacy offices clash over publishing resident datasets, principles, legal counsel, and Product Management belong in a timeboxed strategy that matches stakes—consent, statute, and public transparency. The Scrum Master / Team Coach does not crush that conflict into a same-day story argument. Civic data work requires due process in the conflict design itself.
Timeboxing the values fight into a same-day refinement argument under-scopes legal and ethical stakes. Letting developers pick privacy or open data in standup removes accountable roles. Treating it as a UI-color dispute and picking the lightest strategy misreads intensity and can create unlawful or harmful releases.
Exam caveat: match timebox and participants to conflict type; values/policy conflicts are heavier than preference disputes. Operational check: if resident data publishing is contested, schedule a multi-role working session with legal and Product Management before any publish decision.
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.