A council aide rewards departments that quietly lobby for their own building-permit fee-waiver features off the record. How should the Product Owner model Scrum Values under that pressure?

Product Owners model Scrum Values most visibly when stakeholders reward hidden agendas. If a council aide rewards departments that quietly lobby for building-permit fee-waiver features off the record, the Product Owner should make work and trade-offs transparent, inspect evidence openly, and refuse hidden-agenda ordering even when politics reward opacity. Openness and courage keep permit value decisions empirical and visible to the public interest.

Rewarding hidden agendas by creating a confidential aide track alongside the real Product Backlog institutionalizes a second ordering system. Letting each department's lobbyist reorder the Product Backlog for a week to keep the peace abandons value ordering for political turn-taking. Outsourcing ordering to a political steering vote and stopping attendance at Sprint Review removes Product Owner accountability from inspection.

Exam caveat: PSPO II values questions often place political reward for opacity against Product Owner modeling of transparency and courage.

Operational check: route every fee-waiver request through the visible Product Backlog with an explicit value hypothesis, decline off-record ordering meetings, and show trade-offs openly at Review.