Clarify Your Acceptance Criteria with Gherkin

Acceptance criteria is one of the most powerful tools. A Product Owner can use to ensure that the adult team is building what the customer really wants. That's all well and good, but in my experience acceptance, criteria can be very hard to write, especially if the team and the product owner aren't communicating

Gherkin, also known as GIVEN-WHEN-THEN, is an effective method for writing Acceptance Criteria at many levels in software development. It treats the software as a black box, focusing on the inputs, triggers, and outputs.
In this talk, we’ll cover the basics of writing good GIVEN-WHEN-THEN Acceptance Criteria, give some advice on how to expand beyond your basic use case coverage, and spend some time working through examples.

Matt McConnell is an Agile Coach, Product and Program Manager. He got his start in IT as the cash register guy on the Jo-Ann Fabrics help desk. He’s worked with a number of retail and ecommerce companies before moving over to DoD and Government consulting. As a language geek, his superpower is helping to translate business needs into usable requirements, and translate technical opportunities and risks into something the business can understand. He lives just north of Pittsburgh.