Developers on a utilities billing team find a hidden dependency: the two highest Product Backlog items both need a shared rate-table change that is not yet on the backlog. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
If two top chores both need the same wrench, and the wrench is not even on the list, the list is lying. Put the dependency where people can see it and restack so the work can actually happen. Quiet hallway coordination is how surprises get born.
Full Explanation
Dependencies are a Product Backlog concern, not a private developer inconvenience. The Product Owner should make the dependent work visible and reorder so the team can produce a workable forecast. Hiding dependency work off the backlog destroys transparency. Scrum still applies; empiricism depends on seeing the real order, including constraints.