Recreation-booking value is blocked by a hiring-policy freeze on digital access for park staff, an issue no Scrum Team can lift alone. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Some rocks are too big for the team’s shovel. A hiring-policy freeze on park-staff access is a city-level boulder, not a Sprint task to hide in the code. Put it on an org impediment list and walk it to leadership with the Scrum Master.
Full Explanation
Structural impediments—policy, funding, and cross-department constraints—cannot be removed by team tactics alone. When recreation-booking value is blocked by a hiring-policy freeze on digital access for park staff, no Scrum Team can lift that boulder in the Sprint Backlog. The Product Owner should maintain an organizational impediment list of structural issues and collaborate with the Scrum Master and leadership to remove them. Secret workarounds, cancelling Scrum, or relabeling the freeze as a Product Goal all hide the design problem.
Treating the freeze as a Sprint Backlog workaround Developers must solve in secret fails by hiding a policy blocker in code heroics. Cancelling Scrum events until the policy changes fails by abandoning empiricism. Reordering the Product Backlog to treat the freeze as if it were the Product Goal fails by confusing an impediment with product value intent.
Exam caveat: Org-level policy blockers belong on an impediment list escalated with the Scrum Master, not in secret Sprint tactics. Operational check: Log the digital-access hiring freeze on an org impediment list, quantify blocked recreation-booking value, and schedule a leadership decision path with the Scrum Master.