The Product Owner on the housing-voucher team keeps adding "just this one" mid-iteration, and developers erupt. What is the source of the conflict?

When the Product Owner on a housing-voucher team keeps adding "just this one" mid-iteration and developers erupt, the source of the conflict is broken working agreements about change and WIP—not a story that developers hate residents. The Scrum Master / Team Coach should name the agreement and flow issue so the team can repair how mid-iteration change is handled while still protecting voucher applicants through planned, sustainable delivery.

Treating developers who resist any change as people who should be replaced fails by concept: it personalizes a process failure and ignores WIP and commitment agreements. Calling it a facts dispute about how many vouchers exist citywide fails by concept by mislabeling a working-agreement conflict as a data argument. Blaming an RTE cadence problem as if mid-iteration adds were a train-level ceremony issue fails by concept: iteration change discipline is primarily a team working-agreement matter, not a missing ART ritual.

Exam caveat: SASM conflict analysis distinguishes sources—working agreements, facts, goals, methods, and interpersonal—and mid-iteration scope thrash is classically an agreement/WIP issue. Empathy for residents remains; empathy does not require unbounded mid-iteration adds that burn out the housing-voucher team.

Operational check: facilitate a review of change and WIP working agreements, define how urgent voucher items enter the iteration, make trade-offs explicit, stop framing the conflict as anti-resident sentiment, and verify subsequent mid-iteration requests follow the agreement without eruptions.