User Story Mapping

An installment in Salva O'Renick Lunch & Learn series discussing the concepts of User Story Mapping.

Transcript

1. User story mapping
2. What Why How
3. What First, let’s review User Stories and User Flow
4. user x this occupation these are their goals these are their frustrations these are their personality traits
5. As a (user x), I can ____ _________________________ so that _________________ __________.
6. Next The Flow
7. The Flow how users use the product
8. The Flow how users use the product when they use the product
11. User tasks
12. Groups
13. Build tasks
14. What Why
15. Why comprehensive understanding*
16. Why collaboration
17. Why mutual understanding
18. Why conveying priority
19. Why comprehensive understanding*
20. Why comprehensive understanding*
21. Why comprehensive understanding*
22. Why collaboration
23. "Stories don’t become stories until they’re told." -Jeff Patton
24. User stories
25. User stories CD AD DEV COPY AM PM
26. User stories CD AD DEV COPY AM PM
27. Why mutual understanding
28. Are those all of the metrics that should be included in the Report feature?
29. Are those all of the metrics that should be included in the Report feature? I think so. But we should probably give the user the ability to customize the dates for the time filter.
30. You think so? Why?
31. You think so? Why? Because companies will operate under different sales cycles.
32. Ah good catch. I’ll add it as a feature.
33. Ah good catch. I’ll add it as a feature.
34. Why conveying priority
36. prioritize
37. prioritize
38. What Why How
39. How
40. define objective or jobs to be done 1
41. x user hires our product to do a. ——————————————————— b. ——————————————————— c. ———————————————————
42. define objective or jobs to be done define personas 1 2
43. x user user can do this user can do this user can do this user can do this y user user can do this user can do this user can do this user can do this z user user can do this user can do this user can do this user can do this system
45. define objective or jobs to be done define personas navigate tool linearly as user 1 2 3
53. define objective or jobs to be done define personas navigate tool linearly as user group tasks 1 2 3 4
55. define objective or jobs to be done define personas navigate tool linearly as user group tasks build tasks 1 2 3 4 5
59. define objective or jobs to be done define personas navigate tool linearly as user group tasks build tasks prioritize 1 2 3 4 5 6
62. MVP
63. MVP STOP
66. MVP
67. MVP
68. MVP 1
69. MVP 1 2
71. LET’S MAP