Too Long; Didn't Read
Teams want to put the user in the centre of their product development process while building products. Acceptance criteria document customer expectations, provide an end-user perspective, clarify requirements and prevent ambiguity. When done properly, this will eventually help your quality assurance verify if the development goals were met. In this article I will talk about some of the common mistakes teams make when writing user stories when writing acceptance criteria. It's essential for teams to ensure they write acceptance criteria before the sprint begins — ideally before planning.