The 3 “S’s” of User Stories
summary
Workshop shows a concrete rule set: write each story as one simple sentence with a single interaction and a specific observable outcome so it fits in one sprint. Teams use index cards and sticky notes to co-create and split epics, apply DEEP backlog grooming, and add acceptance criteria as quality gates. Common failures are UX as separate stories, tech tasks mislabeled as user stories, and too-big epics that block delivery.
AI-written summary · about
chapters (7)
- 0:00Workshop introduction
- 1:27What is a user story
- 22:54Problems with user stories
- 33:58The three C's
- 53:10Three S's framework
- 1:00:09Rewriting with three S's
- 1:14:24Q&A
related talks
52mUser Story Office and Other Instrumental Memes
47mHypothesis: Are User Stories Hypotheses?
42mHow Doing the Little Things Well Makes the Big Things Possible
29mYour Team, as Saga
36mDEVELOPER ORIENTED PROJECT MANAGEMENT
53m26 Heuristics For Effective Software Development
16mUsing Stories to Lead Product Teams
08mLightning Talk: A Tale of Two Spirits