Public-works inspection requests currently live in three department ticket queues plus a shared spreadsheet. Directors each pull Developers toward their own list. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Three clipboards and a spreadsheet is not a product—it is a food fight with extra paper. One inspection product gets one ordered backlog, and the Product Owner is the person who owns that order. Parallel lists just let the loudest director win the next pull.
Full Explanation
Scrum uses one Product Backlog per product, ordered by the Product Owner. Multiple departmental queues destroy transparency and invite local optimization at the expense of overall value. Merging competing lists after the fact as a courtesy leaves the dual-source problem in place. Creating fake extra products just to preserve department queues avoids the real ordering decision.