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.
Upcoming SlideShare
What to Upload to SlideShare
What to Upload to SlideShare
Loading in …3
×
1 of 46

Whats Your Skateboard - OSCON

1

Share

User Story Mapping is a valuable tool that gives you strategies to view features alongside the problems they solve. It is a powerful approach that allows many people to prioritize features, regardless of technical expertise. Instead of planning our project as a building that we must build with a strong foundation, we begin to plan as a vehicle. This focus delivers the Most Valuable Features to the customer by answering the question, “What’s Your Skateboard?

Related Books

Free with a 30 day trial from Scribd

See all

Whats Your Skateboard - OSCON

  1. 1. WHAT'S YOUR SKATEBOARD? EMILY STAMEY © PHOTO BY KENNY LOUIE 1
  2. 2. EMILY I'm a PHP developer I've o en worked directly with non- technical product owners and users I workED at a University 2
  3. 3. A PROBLEMATIC PROJECT WORKFLOW 1. Research 2. Develop over several months 3. Deliver something 4. Learn if the big guess was correct 3
  4. 4. INSPIRED BY 4
  5. 5. WHAT IS A STORY MAP? A diagram of a project that tells the story of the people and systems involved in a process. Detail is added as we learn more about the project The map can be built for an existing application or a new application. 5
  6. 6. THE STORY MAP 6
  7. 7. WHO SHOULD STORY MAP? Anyone who knows the process ... Not Just Developers At least one knowledgeable person from each group of stakeholders 7
  8. 8. WHEN TO STORY MAP?   When you have questions Before You begin development 8
  9. 9. WHY STORY MAP? Build shared understanding Encourage full discovery before prototyping Prioritize work to be done as a group *Lowers problems with estimates and feature creep 9
  10. 10. THE BIG PICTURE © PHOTO BY BARNYZ 10
  11. 11. FOCUS DURING DEVELOPMENT © PHOTO BY THEILR
  12. 12. 11
  13. 13. WHERE? A large, clear wall or whiteboard. A place central to the team, at least in the beginning. 12
  14. 14. YOU'LL NEED painter's tape markers post-its (many colors & sizes) 13
  15. 15. A SIMPLE STORY List five tasks you do in order to get to work. Put each one on a post-it provided. 14
  16. 16. MY MORNING AT WORK (FIRST DRAFT) 15
  17. 17. FIND VARIATIONS Pick 3 things that you did today that are different from your normal work routine. 16
  18. 18. MY MORNING AT WORK (REVISED) There are variations between people, days of week, at-home and out-of- town work days 17
  19. 19. BUILDING THE NARRATIVE: USERS Who are the Actors/Users in your morning routine? 18
  20. 20. BUILDING THE NARRATIVE: ACTIVITY GROUPS Sometimes several tasks can be grouped together 19
  21. 21. BUILD THE STORY Let's put them together to build a story of your getting to work! 20
  22. 22. LEARN MORE Risk Assumptions Uncertainty If you cannot elaborate, mark it and revisit 21
  23. 23. CLARIFYING QUESTIONS What could we learn to replace risk with REAL information? Do we really know what has been mapped, or did we fill in assumptions? Are you sure about the story you're telling? 22
  24. 24. LABEL THESE 23
  25. 25. THOROUGH DISCOVERY Understand the full process Understand "why" steps are needed in the process Talk about things inside and outside of the app 24
  26. 26. THOROUGH DISCOVERY Simplify and lower risk at implementation Lowers the questions at the phase of implementation Limits Feature Creep (beginning implementation w/o understanding, new features come in) Better estimates 25
  27. 27. 26
  28. 28. PRIORITIES 27
  29. 29. PRIORITIZING THE PROJECT Who will use this product? What steps must they accomplish for success? Remove/postpone the rest 28
  30. 30. PRIORITIZING FEATURES Differentiator - feature sets you apart from competition Spoiler - moves in on someone else’s differentiator Cost reducer - reduces organizational costs Table stakes - feature necessary to compete 29
  31. 31. FOCUS ON OUTCOMES What are you hoping to do with your application? Prioritize features based on the problem they solve Implement only what solves the problem or meets the objective 30
  32. 32. PROTOTYPING 31
  33. 33. PROTOTYPING What is the smallest thing you could build to prove/disprove an assumption? Sketch & prototype to test viability of the solution Aim for less than minimum, get feedback, and iterate o en When you give prototype to development partners you can include metrics to see what they actually do 32
  34. 34. MVP VS. MOST VALUABLE FEATURES Focus on releasing valuable features every time. Sometimes we plan features in a chronological order Or we divide the project into components 33
  35. 35. WHEN WE BUILD IN PIECES 34
  36. 36. WHEN WE BUILD IN PARTS
  37. 37. 35
  38. 38. INSTEAD WE WANT TO ITERATE!
  39. 39. 36
  40. 40. 37
  41. 41. STRATEGIES 38
  42. 42. 39
  43. 43. SUMMARY A tool you can use with non-technical subject matter experts, customers, etc A visual guide for managing your workload Focus on objectives when you prioritize Plan to deliver a usable product at each deliverable 40
  44. 44. SOOO... 41
  45. 45. WHAT'S YOUR SKATEBOARD? 42
  46. 46. @elstamey THANK YOU! EMILY STAMEY @ELSTAMEY HTTP://ELSTAMEY.COM HTTPS://ELSTAMEY.GITHUB.IO/SKATEBOARD.HTML/#/ 43

×