A User Story is a tool used to provoke and summarize a conversation, between the Team and their Product Owner, for a better understanding of an item on the Product Backlog. The User Story provides context regarding who a Product Backlog Item is being developed for and why it is of value.
It’s important to note that this isn’t part of Scrum per se, but is a tool that grew up beside Scrum and is often used in conjunction. User Stories can be helpful but aren’t required as part of the practice of Scrum.
Life Cycle of a User Story
Story Slicing, How Small is Enough?
More Notes on Story Splitting
Vision to User Stories – What is the Best Flow?
Scrum By Example – The Team Collaborate on Acceptance Criteria
Scrum by Example – How to Deal with Bad User Stories as a ScrumMaster
Resource Links:
- Alternative formats for User Stories
- Another Alternative User Story Format
- Conversational Stories
- Story Slicing: A Real Life Example
- Introduction to User Stories Presentation
- Using Vertical Slicing and Estimation to make Business Decisions at Adobe
- What if the User Story is too Big for the Team?
STORY SPLITTING
- Cargo Cult Requirements – More questions for your User Stories
- Twenty Ways to Split Stories
- Patterns for Splitting User Stories
- Splitting User Stories with Acceptance Criteria
- Splitting User Stories with Generic Words
- Splitting User Stories with Timeline Analysis
- Story Slicing: A Real Life Example
- Story Splitting Poster
ACCEPTANCE CRITERIA
INVEST
USER STORIES BOOKS
- User Stories Applied: For Agile Software Development – Mike Cohn [AMAZON]
