Driving Engagement with User Stories
summary
90-minute workshop condenses a daylong exercise into hands-on practice: write stories on Post‑its, limit each to two cards, run Three Amigos roleplays to derive acceptance tests, and convert those tests into specification by examples / BDD (Gherkin-style scenarios). Emphasizes three Cs — card conversation confirmation — uses Jira only after card work, and frames bugs as missing tests aiming for a zero‑defect flow: if acceptance tests fail, the story doesn’t ship.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:35What are User Stories
- 10:35Definition of User Stories
- 14:15User Story Activity
- 21:45Three Things to Focus on
- 24:35Write a Story
- 26:15Group 3s
- 30:15Recap
- 33:45Adoption of User Stories
- 35:45Peanut Butter Jelly Sandwich
- 49:00Requirements
related talks
37mRevolutionizing Agile Backlog Refinement through Gamification
47mTelling Better Stories with Tests
30mTurning stories into software
39mStop Testing, Start Storytelling
23mGetting The Most Out of Team Exploratory Testing Sessions
17mUnlocking Collaboration in Code: A Journey through BDD
45mLet's talk about software behaviour (BDD)
41mWriting better BDD scenarios