A coach insists every library-holds Product Backlog item must use the As a / I want / So that template or it cannot enter Sprint Planning. Several clear defect reports and a records-retention constraint do not fit the template well. What should the Product Owner do?
Select an answer to reveal the explanation.
Short Explanation
User stories are a useful napkin, not a city ordinance. If a holds defect or a retention rule is already clear, stuffing it into a three-blank template just wastes ink. Scrum cares that the team understands intent, not that every line rhymes.
Full Explanation
Scrum does not prescribe a user-story template. Product Backlog items may be stories, defects, constraints, or other forms as long as intent is clear enough to forecast and build. Mandating one format as a gate delays valuable library work and pretends format equals understanding. The Product Owner should keep whatever representation conveys the outcome, then refine with Developers until the item is ready enough.