High-quality Agile requirements are more than just user stories; they are visual models, testable acceptance criteria, and the result of collaborative facilitated sessions with your stakeholders and team. Given, When, Then (or Gherkin language) is an effective style for documenting acceptance criteria, particularly in support of teams engaged in behavior-driven development processes.
In this interactive discussion, we will talk about what it takes to get to a “good” user story. We start with visual models that help identify and prioritize the right user stories and use proven techniques to elaborate stories into solid acceptance criteria in the Gherkin format (that could be consumed by automation tools like Cucumber). We then take a real world example from idea to “ready” requirement, so you can walk away from this session with hands-on experience at crafting user stories that are ready for the team and testable.
