From the course: Agile Product Owner Role: Techniques

Unlock the full course today

Join today to access over 22,600 courses taught by industry experts or purchase this course individually.

Acceptance criteria

Acceptance criteria

From the course: Agile Product Owner Role: Techniques

Start my 1-month free trial

Acceptance criteria

- So how do we know the user story will meet all of the users expectations? Teams define this with acceptance criteria, which are the conditions that tell us when the user story is working as intended and satisfying the customer. Although the team may define it altogether, the product owner plays the main role in deciding on this acceptance criteria. These conditions are typically created and owned by the product owner and are attached to the user story. Acceptance criteria help the team define what success looks like from a user perspective instead of a it's been coded perspective. Acceptance criteria are typically a list of statements that have a clear result. Think of them like statements you could build to test the product. They might contain scenarios, rules, and logic that create a specific outcome for a user. Or there might be nonfunctional requirements like security, performance, expected volumes, response times, and thresholds of performance. I like to keep acceptance…

Contents