A Definition of Ready checklist for the public-works inspection app now requires signed UX comps, a legal memo, and a cost-benefit PDF before any item may enter Sprint Planning. Work has stalled. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
Ready should be a light backpack, not a locked vault. If inspectors cannot start until Legal, UX, and Finance all stamp a PDF, you have reinvented waterfall and called it Scrum. Pack just enough so the next Sprint can move—then learn the rest on the job.
Full Explanation
Helpful readiness means near-term items are understood well enough to forecast. A bureaucratic Definition of Ready that demands signed design, legal memos, and business cases before any Sprint starts stops empiricism. The Product Owner should keep lightweight collaboration with Developers instead of a stage-gate. Permanent deferral and PMO handoffs recreate predictive projects rather than inspect-and-adapt delivery of inspection value.