Learn to define exactly when a user story is "done" by writing testable, unambiguous acceptance criteria. Master the Given/When/Then (Gherkin) structure, choose between scenario and rule-based styles, and build a reusable template that ends the "but that's not what I meant" argument.
Watch the free preview
The hidden cost of ambiguous "done" — free to watch, no account needed.
What you'll learn
- Explain what acceptance criteria are and how they differ from the Definition of Done
- Write testable, unambiguous criteria using the Given/When/Then (Gherkin) structure
- Choose between scenario-based and rule-based styles for a given story
- Cover happy paths and edge cases so "done" cannot be disputed after delivery
- Build and apply a reusable Acceptance Criteria template for your own backlog
Syllabus
The Boundary of Done
The hidden cost of ambiguous "done"Free preview
Acceptance criteria versus the Definition of Done
The Given/When/Then Technique
Given, When, Then — the structure of a testable criterion
Scenario-based and rule-based styles
Applying Criteria to Real IT Work
Writing complete criteria for a real story
Case study — a "done" story the team could not agree on
Making Criteria Stick
Building your Acceptance Criteria template
Traps and anti-patterns to avoid