Does your team ever write scenarios that seem implementation heavy? How about scenarios that feel too vague? This session will take attendees through the art of decomposing user stories into well formed automatable acceptance criteria, from the point of view of a developer and a product owner. Together we will explore the gherkin syntax (given/ when/ then), the trades offs that exists when we change the words we use, and how this can affect the software you build. Attendees will walk away from this session armed with information to help them write better gherkin and make better informed decisions around the words they use.