A library digital-card Product Backlog has become a junk drawer of branch wishes, vendor tickets, and one-off reports, and there is no Product Goal. What should the Product Owner establish first?
Select an answer to reveal the explanation.
Short Explanation
A backlog without a Product Goal is a junk drawer—easy to toss in another charger, impossible to say what finished looks like. The Product Goal is the commitment that says what this library card product is trying to become. Once that is clear, half the drawer does not belong.
Full Explanation
The Product Goal is the Scrum commitment for the Product Backlog; it describes a future state of the product that the Scrum Team plans to achieve. Without it, ordering is political inventory rather than progress toward a cardholder outcome. The Product Owner should establish a single Product Goal and use it to include, exclude, and sequence items. Documentation baselines, velocity commitments, and never-say-no Kanban boards do not restore that commitment.