From the course: Agile Requirements Foundations
Unlock this course with a free trial
Join today to access over 25,300 courses taught by industry experts.
Acceptance criteria
From the course: Agile Requirements Foundations
Acceptance criteria
- So, how do we know the user story will meet all the user's expectations? And where do all the details go for this user story? Teams define this with acceptance criteria which are all the conditions that tell us when the user story is working as intended and satisfying the customer. Although the team may define it together, the BA plays the main role in generating and documenting these acceptance criteria conversations. These conditions are typically created and owned by the product owner, with the BA doing much of the heavy lifting, and they're attached to a user story. Acceptance criteria help the team define what success looks like from a user perspective. Acceptance criteria are typically a list of statements that have a clear result. Think of them like statements you could build a test to, to test the products. They might contain scenarios, rules and logic that create a specific outcome for a user, or there might be non-functional requirements like security, performance…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.