Sprint Planning for a public-health case-management product fails because Developers do not understand the top Product Backlog items. Stakeholders blame Planning for running too short. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
If Planning is where people first read the work, the homework never happened. Refinement is the ongoing chat that makes the top of the list make sense before the whistle. Stretching Planning into a design workshop just hides the missing collaboration.
Full Explanation
Product Backlog refinement is an ongoing collaborative activity between the Product Owner and Developers so that Sprint Planning can produce a forecast and a Sprint Goal. When items are not understood, the fix is better refinement, not turning Planning into a specification workshop or skipping conversation in favor of a packet. Estimation without shared understanding is theater. The Product Owner cannot delegate that understanding to the Scrum Master.