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
- Examples of User Stories
- Not Everything Needs to Be a User Story: Using FDD Features
- Introduction to User Stories Presentation
- User Stories and FDD
INVEST
USER STORIES BOOKS
See Also:
Acceptance Criteria
User Story Splitting
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This content is created and the links are curated through the lens of Agile Pain Relief Consulting's view of what is effective in the practice of Scrum and Agile. We don't accept submissions and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won't amount to anything more than a cup of coffee in a year.« Back to Glossary Index
