Adaptive Planning Beyond User Stories
summary
Argues that user stories must become survivable experiments with clear selection criteria, not backlog tokens; recommends spending five minutes per story to specify the observable behavior change and rejection criteria. Shows a mind‑mapping collaboration product that migrates to Google Realtime API and where one checkbox unlocks university-wide access and triggers a spike toward 1,000,000 users. Recommends impact mapping, story maps and hierarchical backlogs, and warns against 500‑item Jira lists that hide commitment.
AI-written summary · about
chapters (19)
- 0:00Intro
- 1:00Senior Business Stakeholders
- 4:00Flexibility
- 6:00Strategic bomber
- 7:50User story
- 11:50Flexible scope
- 13:25Product ownership
- 16:05AB Large Ship
- 18:15Unpredictable Dimensions
- 24:05Roadmaps
- 27:50Plan to Learn
- 29:20Translate User Stories
- 29:50Selection
- 35:30Survivability
- 36:20Flexible tickets
- 39:55Survivor of experiments
- 41:00Impact mapping
- 43:15Core principles
- 45:30Questions
related talks
21mTelling the Full Story - Use Cases and User Stories
49mBack to Basics: User Story Mapping, the PO's Swiss Army Knife
46mThe final frontier - how to engage business users in agile.
43mBeyond Discovery: A Service Designer's Guide to Agile Delivery
34mVisionary meets the product owner
47mExperience Maps—Empowering Designers in Agile Teams to Navigate and Address UX Debt
47mBe Ready, Be Done: The Art of Slicing User Stories
53mOutcome-based product planning