Writing Better User Stories
User Stories are Product Backlog Items that are descriptions of functionality. The User Story always takes the form:
"As a ______ I want to ___________ so that I can ______."
Our experience has shown that when Teams master producing clear, independent, and achievable User Stories their Velocity generally doubles.
Estimated time for this course: 90 minutes
Suggested Prerequisites: Business Value
Upon completion you will:
- Be able to write User Stories as independent vertical slices of functionality
- Be able to write Stories with just enough detail while not being prescriptive
- Understand how to estimated and size stories that fit in a single sprint
- Be able to write stories with acceptance criteria and Definitions of Ready and Done
- Qualify for Scrum Alliance SEUs and PMI PDUs. See FAQ for detail
ScrumLab PrimePrime members enjoy unrestricted access to all our webinars and advanced Scrum topics. It includes clear definitions and insightful videos from the inventor of Scrum on the most advanced topics in the agile community.
Writing Better User Stories Overview:
Frequently, new Teams have difficulty getting User Stories small enough and sufficiently specific. This should improve with time. Developing good User Stories is the job of the Product Owner. Writing User Stories so that they are explicit and granular needs to be done in close consultation with the Scrum Master and the Team. Good, achievable User Stories may be the most important variable in Sprint Velocity. Often user stories may have multiple functions imbedded in them. In Scrum, these are called epics. From a Product Owners point of view, revenue comes from large pieces of functionality that can be shipped to a customer. However, for implementation, Epics need to be broken down into multiple stories.
Origins of User Stories:
The Scrum Guide defines the Product Backlog as an ordered list of Product Backlog Items. The User Story concept was developed by the original XP team at Chrysler. Ward Cunningham presented an Epidsodes pattern language at a 1995 conference which outlined the initial concept of a user oriented requirement. Discussion ensued on the XP list for the next few years and user stories were in Kent Beck's first book on eXtreme Programming in 1999. The user story approach is so useful it has been widely adopted throughout the Agile community. About 80% of Scrum teams worldwide create user stories for Product Backlog Items.