Clerks need a way to void a mistaken parking ticket in a new citation system. What should accompany the user story so the team knows when the need is met?
Select an answer to reveal the explanation.
Short Explanation
A user story without acceptance criteria is like a fix-my-bike sticky note with no definition of done. Clerks need voiding that is actually checkable, not just a vague wish. Acceptance criteria spell out the pass-fail conditions for voiding a mistaken ticket.
Full Explanation
User stories describe who needs what and why in business language. Acceptance criteria make each story testable by stating observable conditions that must be true for the need to be met. Without those criteria, a clerk voiding story remains ambiguous for builders and testers. Schedule graphics, marketing brochures, or unrelated RACI charts do not prove the void capability works.