Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

User Story Mapping


Published on

The latest version of this presentation as presented at PrairieDevCon West in Calgary, 2012.

Published in: Technology, Design
  • Be the first to comment

User Story Mapping

  1. 1. User Story Mapping:Rounding OutYour Backlog
  2. 2. Group Group GroupTask Task Task Task Task Task
  3. 3. Jeff Patton
  4. 4. Steve Rogalsky@srogalsky Continuous Improvement Process Hacker Family Agile Teaching People First Application Architect Inclusive Models Problem Solving Coach Test First Change Agent Lean Retro Cartoon Fan 5 5
  5. 5. What’s the problem?
  6. 6. What User Stories are notTasks • Create user table • Create password encryption service • Create login service • Create CSS • Create page template • Add login button
  7. 7. What User Stories are notBig* • Login page • “the web site” • 160 hours of effort* Exception – stories that are in the distance can be big. These stories willshrink in size and grow in detail as they get closer to being implemented.
  8. 8. What User Stories are notUse cases • Login Use Case – Happy path: • Login w/ valid pwd – Alternate Paths: • Login w/ invalid pwd • Forgot password • Reset password • Password rules A use case will often contain many user stories
  9. 9. What User Stories are notA document • Login.docx • “this document, by its very size, ensures that it will never be read.” – Sir Winston Churchill
  10. 10. What User Stories are…A small piece of • As a user, I want tofunctionality that login with myprovides some value to password, so that Ia user can gain access to the site. “A place holder for a conversation.”
  11. 11. FormatsBy the book:As a [role], As a [mom]I want to I want to[some action], [login with my pwd]so that so that[goal] [I can gain access to the site]
  12. 12. Formats As aWho [mom] I want toWhat [login with my pwd] so thatWhy [I can gain access to the site]The “by the book” format is great for learning, but at its core, it is just Who/What/Why
  13. 13. UserStories gohere
  14. 14. How to do it?1. Divide into groups of 3-5 people2. Start by gathering “things people do” – the tasks. Write themdown individually and then read them aloud to your group – Likely they start with a verb. – These are high level user stories called “Tasks” (walking skeleton) – This forms your story map skeleton3. Group them silently (simply because it is faster)4. Name the groups and lay them out in order of time (left toright) – These are called “User Activities” (backbone)5. Add more detailed user stories below the main tasks6. Prioritize top to bottom7. Break into releases
  15. 15. How to do it?smithcdau (@smithcdau)11-08-11 2:12 PMRT @shanehastie: @jeffpatton if youre arguingabout sequence it probably means it doesntmatter. #Agile2011 #yam
  16. 16. Sowhat?
  17. 17. Some Definitions PrioritiesTimeUser Activities (Backbone)User Tasks (WalkingSkeleton) User Stories Releases
  18. 18. Iterative1 2 3 4 5 Incremental Credit: Jeff Patton
  19. 19. ,
  20. 20. Wrap Up• Make better decisions• Increase your ability to delivery• Allay fears of agile sceptics
  21. 21. Links• Two articles from Jeff: – klog.html – slice_it.pdf• Online User Story Mapping: –• DotNetRocks podcast: – 750
  22. 22. THANKS! Questions?Contact @srogalsky winnipegagilist.blogspot.com
  23. 23. Whyslice?User StorySlices gohere:
  24. 24. How not to Slice?Tasks • Create user table • Create password encryption service • Create login service • Create CSS • Create page template • Add login button
  25. 25. How to Slice?• By screen (for basic screens • By priority only) • By applying the INVEST• By button model• By group of fields • By acceptance criteria• By workflow step • By option• Optional workflow steps • By role• Validation • By Subjective quality• Error handling * (never by objective• Admin functions (maintaining quality: always be drop downs, etc) defect free) • By value