- A User Story Primer
- The Art of Agile Development: Incremental Requirements
- The Art of Agile Development: Stories
- How I talk about User Stories
- User Story versus Requirement and Specification
- What’s in a Story?
Writing User Stories
- Writing Good User Stories
- User Story Examples and Counterexamples
- Imperative vs Declarative Scenarios in User Stories
- They’re not User Stories
- so that… so what?
- Fixing the Cause-Effect Trap in User Stories
- Technical implementation heavy stories
- Customer and Developers collaborate on user stories
- Thin slice
Sizing User Stories
- Story Sizing: A better start than planning poker
- Half-point planning cards?! “Khan!!!!!!!!!!!!!!”
- Story slicing: How small is enough?
- Product Sashimi is delicious!
- When is the story too big?
- Agile antipattern: Taking on large stories
- Patterns for Splitting User Stories
- How to split user stories
- 10 strategies to split large user stories
Using User Stories
- How we use stories
- Beyond Story Cards: Agile Requirements Collaboration
- Conversational Stories
- Scrum Anti-pattern : Prioritizing Stories Within Sprints
- Scrum Anti-Pattern: NOT Prioritising Stories Within Sprints
- Prioritising stories within a sprint?
- Features != User Stories
- Should Story Points Be Assigned to A Bug-Fixing Story?
- Why We Don’t Write User Stories Anymore
- Don’t Forget EVIL User Stories
- A user story is the title of one scenario whereas a use case is the contents of multiple scenarios
- Why I still use use cases
- Structuring use cases with goals
- Agile Software Requirements: Use Cases
Minimal Marketable Features