Telling the Full Story - Use Cases and User Stories
summary
Argues that writing user stories alone produces stitched, fragile systems and that teams should turn user stories into use cases before sprint work. Recommends building an actor diagram, detailed step lists with step-by-step alternative paths, and a summary of preconditions, postconditions and success criteria. Notes this is time consuming and requires team input, but yields reliable sprint-sized stories, straightfoward QA test scripts, clearer prioritization when over budget, and far fewer surprises at handoff.
AI-written summary · about
chapters (20)
- 0:00Introduction
- 0:34Overview
- 1:00User Stories
- 1:33User Stories Benefits
- 2:03Collecting Information
- 2:26Staying Focused
- 2:40Limitations
- 3:03Inconsistent Requirements
- 3:44Narrow sighted
- 5:48Use Cases
- 7:41Sample Steps
- 8:56Downside of Use Cases
- 9:33Writing User Stories
- 10:45B Hat Testing
- 12:58Living Document
- 13:21Resources
- 16:25Templates
- 16:40Template
- 17:01Delegate
- 20:21Solution
related talks
56mAdaptive Planning Beyond User Stories
49mBack to Basics: User Story Mapping, the PO's Swiss Army Knife
43mBeyond Discovery: A Service Designer's Guide to Agile Delivery
47mHypothesis: Are User Stories Hypotheses?
43mWhen Wishing Still Helped... What Folklore Can Teach Us About Technical Writing
46mThe final frontier - how to engage business users in agile.
44mWhat to Build First: Defining MVP with Scenarios
34mVisionary meets the product owner