Acceptance Criteria
Acceptance Criteria are used to ensure that a feature (or User Story) the team is building meets the needs of the End User. The common practice is for team members to collaborate on writing a series of examples that demonstrate the expected behaviours of a feature.
There is no required structure for acceptance criteria, although many in Behaviour Driven Development world use: Given, When, Then.
Given: My bank account has a balance of $100 When: I attempt to withdraw $101.01 Then: I get no money and error
When to create? Some teams do this in refinement, others right after Sprint Planning.
Who is involved: Team members (a minimum of 3 perspectives), Product Owner (sometimes a participant, sometimes as a reviewer), Stakeholders (occasionally as reviewers).
