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

4,449 views

Published on

Rounding out your backlog.

Published in: Technology
  • Be the first to comment

User Story Mapping

  1. 1. (Track Sponsor)<br />User Story Mapping – Rounding out your Backlog<br />Steve Rogalsky<br />@srogalsky<br />winnipegagilist.blogspot.com<br />
  2. 2. Agree / Disagree / Not Sure<br />Credit: Monty Python Argument Clinic<br />
  3. 3. Outcome: Demonstrate the ability to create a User Story Map<br />
  4. 4. About Me<br />Agilist and team member at Protegra in Winnipeg <br />(It says “Application Architect” on my business card)<br />Founder of Winnipeg Agile User Group<br />@srogalsky<br />http://winnipegagilist.blogspot.com<br />
  5. 5. Learning Outcomes<br />Demonstrate the ability to create a User Story Map<br />(You’ll create three)<br />Explain what a user story is (and isn’t)<br />Demonstrate the ability to slice user stories in your map<br />Describe the benefits of User Story Mapping<br />Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  6. 6. Outcome: Explain what a user story is (and isn’t) <br />
  7. 7. What User Stories are not<br />Tasks<br />Create user table<br />Create password encryption service<br />Create login service<br />Create CSS <br />Create page template<br />Add login button<br />Outcome: Explain what a user story is (and isn’t) <br />
  8. 8. What User Stories are not<br />Big*<br />Login page<br />“the web site”<br />160 hours of effort<br />* Exception – stories that are in the distance can be big. These stories will shrink in size and grow in detail as they get closer to being implemented.<br />Outcome: Explain what a user story is (and isn’t) <br />
  9. 9. What User Stories are not<br />Use cases<br />Login Use Case<br />Happy path:<br />Login w/ valid pwd<br />Alternate Paths:<br />Login w/ invalid pwd<br />Forgot password<br />Reset password<br />Password rules<br />A use case will often contain many user stories<br />Outcome: Explain what a user story is (and isn’t) <br />
  10. 10. What User Stories are not<br />A document<br />Login.docx<br />“this document, by its very size, ensures that it will never be read.” – Sir Winston Churchill<br />Outcome: Explain what a user story is (and isn’t) <br />
  11. 11. What User Stories are…<br />A small piece of functionality that provides some value to a user<br />As a user, I want to login with my password, so that I can gain access to the site.<br />“A place holder for a conversation.”<br />Outcome: Explain what a user story is (and isn’t) <br />
  12. 12. What User Stories are…<br />I Independent *<br />N Negotiable (can be prioritized)<br />V Valuable (to a user)<br />E Estimable<br />S Small<br />T Testable<br />Outcome: Explain what a user story is (and isn’t) <br />
  13. 13. Formats<br />By the book:<br />As a [role], <br />I want to <br />[some action], so that <br />[goal]<br />As a [user] <br />I want to <br />[login with my pwd] <br />so that <br />[I can gain access to the site]<br />Outcome: Explain what a user story is (and isn’t) <br />
  14. 14. Formats<br />Who<br />What<br />Why<br />As a <br />[user] <br />I want to <br />[login with my pwd] <br />so that <br />[I can gain access to the site]<br />The “by the book” format is great for learning, but at its core, it is just Who/What/Why<br />Outcome: Explain what a user story is (and isn’t) <br />
  15. 15. Formats<br />Title; Sentence; Acceptance Tests<br />Title: Login w/ pwd<br />Login w/ password and show welcome page<br />Test upper, lower, numbers, special characters, accents, spaces<br />Test mandatory lengths<br />Test invalid pwds<br />Outcome: Explain what a user story is (and isn’t) <br />
  16. 16. Formats<br />Lean Startup:<br />Feature <br />[X]<br />will move Metric <br />[Y]<br />Feature <br />[show sad face before logging off] <br />will move Metric <br />[time spent logged into the site]<br />Outcome: Explain what a user story is (and isn’t) <br />
  17. 17. Outcome: Explain what a user story is (and isn’t) <br />
  18. 18. Take the Bluecards and re-sort them<br />Outcome: Explain what a user story is (and isn’t) <br />
  19. 19. Outcome: Demonstrate the ability to slice user stories in your map<br />
  20. 20. Why slice?<br />User Story Slices go here:<br />Outcome: Demonstrate the ability to slice user stories in your map<br />
  21. 21. How not to Slice?<br />Outcome: Demonstrate the ability to slice user stories in your map<br />Tasks<br />Create user table<br />Create password encryption service<br />Create login service<br />Create CSS <br />Create page template<br />Add login button<br />
  22. 22. How to Slice?<br />By screen (for basic screens only) <br />By button <br />By group of fields <br />By workflow step <br />Optional workflow steps <br />Validation <br />Error handling *<br />Admin functions (maintaining drop downs, etc) <br />By priority <br />By applying the INVEST model <br />By acceptance criteria <br />By option <br />By role <br />By Subjective quality (never by objective quality: always be defect free) <br />By value<br />Outcome: Demonstrate the ability to slice user stories in your map<br />
  23. 23. Other Tips<br />Keep them as stories!<br />Slice them small when needed, but don’t get silly<br />Slice any time<br />When you are fighting over your planning poker estimates – slice away.<br />Slice more liberally if the story is higher priority<br />Outcome: Demonstrate the ability to slice user stories in your map<br />
  24. 24. Outcome: Demonstrate the ability to slice user stories in your map<br />Take the Purplecards and re-sort them<br />
  25. 25. Outcome: Demonstrate the ability to create a User Story Map<br />User Activities<br />User Tasks<br />User Stories<br />
  26. 26. Outcome: Demonstrate the ability to create a User Story Map<br />Time<br />Priorities<br />Releases<br />
  27. 27. Outcome: Demonstrate the ability to create a User Story Map<br />
  28. 28. Outcome: Describe the benefits of User Story Mapping<br />
  29. 29. Outcome: Describe the benefits of User Story Mapping<br />
  30. 30. Outcome: Describe the benefits of User Story Mapping<br />
  31. 31. Outcome: Describe the benefits of User Story Mapping<br />
  32. 32. How to do it?<br />1. Divide into groups of 3-5 people<br />2. Start by gathering “things people do” – the tasks. Write them down individually and then read them aloud to your group<br /><ul><li>Likely they start with a verb.
  33. 33. These are high level user stories called “Tasks” (walking skeleton)
  34. 34. This forms your story map skeleton</li></ul>3. Group them silently (simply because it is faster)<br />4. Name the groups and lay them out in order of time (left to right)<br /><ul><li>These are called “User Activities” (backbone)</li></ul>5. Add more detailed user stories below the main tasks<br />6. Prioritize top to bottom<br />7. Break into releases<br />Outcome: Demonstrate the ability to create a User Story Map<br />
  35. 35. Outcome: Demonstrate the ability to create a User Story Map<br />
  36. 36. Outcome: Demonstrate the ability to slice user stories in your map<br />
  37. 37. Outcome: Describe the benefits of User Story Mapping<br />Take the Greencards and re-sort them<br />
  38. 38. Iterative<br />1<br />2<br />3<br />4<br />5<br />Incremental<br />Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />Credit: Jeff Patton<br />
  39. 39. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  40. 40. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  41. 41. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  42. 42. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  43. 43. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  44. 44. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  45. 45. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  46. 46. Iterative vs. Incremental<br />Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  47. 47. Iterative Advantages<br />Validate your architecture and solution early <br />See and test the whole application early <br />Encourages important stories to be built first <br />Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  48. 48. Iterative Advantages<br />Elicits improved feedback on the whole application early <br />Deliver your application early as early as possible<br />Discourages "gold plating" <br />Helps contain scope<br />Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  49. 49. Iterative Disadvantages<br />Your code and design has to be change tolerant <br />You have to be proficient at slicing your user stories <br />You won't know the final solution at the beginning of the project <br />Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  50. 50. Outcome: Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />Take the Pinkcards and re-sort them<br />
  51. 51. Our Final Map<br />As a table, choose 2 of the outcomes<br />Outcome: Demonstrate the ability to create a User Story Map<br />Demonstrate the ability to create a User Story Map<br />Explain what a user story is (and isn’t)<br />Demonstrate the ability to slice user stories in your map<br />Describe the benefits of User Story Mapping<br />Explain the difference between iterative and incremental and how that relates to User Story Mapping<br />
  52. 52. Questions?<br />THANKS!<br />Contact Info<br />steve.rogalsky@protegra.com<br /> @srogalsky<br />winnipegagilist.blogspot.com<br />http://www.slideshare.net/SteveRogalsky/?????/<br />

×