A vocal council aide demands a low-value vanity feature jump the citizen-reporting backlog. What should the team avoid?
Select an answer to reveal the explanation.
Short Explanation
Loud isn’t the same as valuable—like the squeakiest hinge getting oil while the bridge bolts wait. Keep backlog authority with the Product Owner and rank by value/risk, not decibels. Hear everyone; don’t invert priority for noise alone.
Full Explanation
When a vocal council aide demands a low-value vanity feature jump the citizen-reporting backlog, the team should avoid priority inversion that lets volume of complaints override Product Owner backlog authority and value-based order. Loud requests still deserve respectful handling, but noise alone should not displace higher-value citizen-reporting work without a Product Owner value judgment. Documenting the request, comparing value, and explaining ranking methods remain healthy stakeholder practices.
Documenting the aide’s request for Product Owner review is appropriate engagement, not something to avoid. Comparing the feature’s citizen value against current top backlog items is proper analysis, not something to avoid. Explaining MoSCoW or risk-value ranking in plain language to elected offices is good stakeholder communication, not something to avoid.
Exam caveat: The anti-pattern is priority inversion from complaint volume; engagement, value comparison, and ranking education remain correct responses. Operational check: log the vanity request, have the Product Owner compare citizen value to current top reporting items, communicate the ranking decision respectfully, and keep the backlog order value-based.