Sprint Planning for an emergency-alert product produces a scattered task list—banner colors, a vendor patch, and an unused CSV export—with no Sprint Goal. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
A Sprint without a Sprint Goal is a grocery run with no dinner in mind—mustard, light bulbs, and no meal. Help the whole Scrum Team name the one alert outcome this Sprint is for. Then the task list either supports that outcome or it does not.
Full Explanation
The Sprint Goal is the commitment for the Sprint Backlog and provides coherence so Developers can negotiate scope as they learn. A scattered task list without that commitment turns the Sprint into unfocused output. The Product Owner participates in crafting the Sprint Goal with the Scrum Team during Planning; it is not a private mandate or a set of individual goals. Coherence toward a valuable emergency-alert outcome is the test.