A municipal open-data portal Product Owner keeps the real Product Backlog in a hidden personal spreadsheet while the team board shows only this Sprint's tasks. Stakeholders cannot see upcoming order. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A secret spreadsheet is a menu the kitchen will not show the dining room. Nobody can inspect what open-data set comes next, so they cannot help adapt. Transparency is not niceness—it is how empiricism works.
Full Explanation
Artifact transparency is a prerequisite for inspection and adaptation. A hidden Product Backlog prevents stakeholders and Developers from understanding order, trade-offs, and progress toward the Product Goal. The Product Owner should make one Product Backlog visible and current. Shielding order from politics, substituting a memo, or handing Product Backlog accountability to the Scrum Master all reduce transparency rather than restore it.