Abstract: Aristotle once said "Well begun is half done." User Stories need 3 C's to get the team going, not two. Don't skip the Confirmation/Acceptance Criteria!
There is help for Product Owners (or BA's) who want to write good acceptance criteria. ATDD and BDD suggest writing these acceptance tests in Gherkin notation. Given-When-Then may seem odd or intimidating at first glance, but it gets easier with understanding and practice. Writing good acceptance criteria for User Stories requires looking at Requirements in a slightly different way.. and maybe picking a tester's brain too.
Join Agile Coach and Testing consultant, Paul Carvalho, as he shares insights, models and tips to help you embrace the art of writing good tests to help get your teams started on the right track. Learn new ideas and techniques to help you get the most from your Product Backlog Refinement activities to benefit your teams and customers.
Learning Outcomes: - Help Product Owners write clear acceptance criteria for user stories
- Overcome the fear of Given-When-Then format for acceptance criteria
- What Testers should know that they don't know about how they can help their teams learn to test better
Attachments:
