On a transit real-time-arrivals product, Developers keep pulling refactor tickets from a private tech queue that never appears on the Product Backlog, while rider-facing reliability work stalls. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A hidden tech queue is a second kitchen nobody can see from the dining room. Refactors that make buses show up on time are product work, not a side hobby. Put that work on the one backlog and order it for the rider value it unlocks—not as an unmanaged stash.
Full Explanation
Technical work that enables product value belongs on the Product Backlog, where it competes transparently with other items. A private tech queue hides opportunity cost, lets low-value chores crowd out reliability, and splits ordering accountability. The Product Owner collaborates with Developers to understand which technical items reduce risk or unlock rider outcomes, then orders those items accordingly. Banning technical work or delegating it to a separate manager recreates dual sources of truth instead of one ordered product.