Hypothesis: Are User Stories Hypotheses?
summary
The talk argues that user stories should be treated as hypotheses and experiments rather than fixed requirements. It discusses the problem that treating requests as certain indicators of value can be misleading in complex, dynamic environments, and shares practical approaches for handling user stories as testable assumptions.
AI-written summary · about
chapters (10)
- 0:00Welcome
- 3:15User Stories as hypotheses
- 8:08Why develop products?
- 13:01Problems and solutions
- 18:50User Stories as experiments
- 24:10Running experiments
- 28:50Experiment challenges
- 31:23Measurement and evaluation
- 35:58Summary
- 37:21Q&A
related talks
21mTelling the Full Story - Use Cases and User Stories
56mAdaptive Planning Beyond User Stories
01h 24mThe 3 “S’s” of User Stories
54mHypothesis Validation: What We Learned from Breaking Bad, Heisenberg and Real Life
52mUser Story Office and Other Instrumental Memes
30mHypothesis - Driven Development in action
05mThe one true driver of DevOps: value hypothesis testing
28mThe lean architect: Experimenting your way to better decisions