User stories

1. All About Those
User Stories
Carlo Ibarra

2. Requirements

3. What is a User Story?
 a written description of the story used for planning and as a reminder to
discuss
 detail of the story
 tests that convey and document details and used to test if story is complete
 system of managing requirements in an iterative development
 3 Cs - Card, Conversation, Confirmation

4. What Stories are NOT?
 NOT a detailed requirement
 NOT a technical specification
 NOT a documented contract
 NOT a software development plan (not SCRUM)
 NOT IEEE 830
 NOT Use Cases
 NOT Scenarios

5. Parts of a User Story
 Description
 User role
 Business function/behaviour
 Business value
 Constraints
 Details
 Acceptance criteria

6. What Makes a Good Story
 a central character (user role)
 a plot - (function/behaviour)
 an ending - (test criteria)
 a lesson - (value to customer)

7. Writing User Stories
 Independent
 Negotiable
 Valuable to Customer/User
 Estimatable
 Small
 Testable

8. Independent
 Loosely coupled
 Stand-alone
 Avoid dependencies

9. Negotiable
 Emergent
 Encourages conversation
 Avoid creating "should have" or "must have"

10. Valuable (to Customer)
 Avoid technical requirements
 Aim for conversation
 Avoid zero-sum game

11. Estimatable
 Stories uses domain parlance and is understood by everyone
 Avoid jargons
 Helps development

12. Small and Testable
 Right size
 Clear criteria for doneness
 functional

13. Guidelines for Good User Stories
 Start with Goal Stories
 Slice the Cake
 Write Closed Stories
 Put Constraints on Cards
 Size the Story to the Horizon
 Keep the UI Out as Long as Possible
 Some Things Aren’t Stories
 Include User Roles in the Stories
 Write for One User
 Write in Active Voice
 Customer Writes
 Don’t Number Story Cards
 Don’t Forget the Purpose

14. Story Smells
 Stories Are Too Small
 Interdependent Stories
 Goldplating
 Too Many Details
 Including User Interface Detail Too Soon
 Thinking Too Far Ahead
 Splitting Too Many Stories
 Customer Has Trouble Prioritizing
 Customer Won't Write and Prioritize the Stories