As a parks recreation-booking product scales, the city creates a requirements bureau that writes and sequences backlog items, leaving the Product Owner to communicate them to the teams. What should the candidate identify?
Select an answer to reveal the explanation.
Short Explanation
A requirements bureau above the Product Owner is a waterfall intake desk with a new badge. The Product Owner is supposed to own order and value on the parks booking product, not read someone else's list into the teams. Scaling should not steal that accountability.
Full Explanation
Scaling structures must preserve the Product Owner's accountability for maximizing value and for the Product Backlog. A bureau that writes and sequences items above the Product Owner recreates a requirements hierarchy and severs empiricism from the person who should adapt order. The Product Owner may collaborate with analysts and stakeholders, but those people do not replace Product Backlog accountability. Making the Product Owner a scribe or placing the Scrum Master under the bureau deepens the anti-pattern.