A (Story Map) is worth a thousand words
•
2 likes•1,510 views
The document discusses story mapping and its benefits over traditional documentation methods. It provides a brief history of requirements documentation and introduces story mapping as a human-readable, visual aid that reflects the user experience. An example story map for a sedan booking app is presented, showing how stories can be organized into categories and estimated with story points. The document then covers delivering in minimum viable product increments and using story maps to plan sprints, before concluding with thoughts on the challenges of shared understanding and conversation over documentation.
Recommended
Recommended
More Related Content
Similar to A (Story Map) is worth a thousand words
Similar to A (Story Map) is worth a thousand words (20)
Recently uploaded
Recently uploaded (20)
A (Story Map) is worth a thousand words
- 2. @elliotsusel
- 3. WHOAREYOU? PRODUCT OWNER OR MANAGER SCRUM MASTER OR PROJECT MANAGER SOFTWARE ENGR OR QA ENGR UI OR UX DESIGNER
- 4. AGENDA Documentation - a brief history Story Mapping Breakout Delivery Q&A
- 6. 30BA completely unscientific estimation of the # of Tears shed over requirements that start with “The System Shall”
- 13. STORY MAPPING
- 14. STORYMAP= SCOPE DOC HUMAN-READABLE HIGH-LEVEL VISUAL AID SIMPLE REFLECTS USER EXPERIENCE
- 15. Story Mapping (as I learned it)
- 16. Registration Booking Payment Enter Contact Information Add Credit Card Set Password In-app Payment Confirmation Receive updates on my Sedan Charge Credit Card Set pickup details Email Receipt to Rider Confirm Pickup Details SEDAN BOOKING APP
- 17. STORYMAP= SCOPE DOC HUMAN-READABLE HIGH-LEVEL VISUAL AID SIMPLE REFLECTS USER EXPERIENCE
- 18. Registration Booking Payment Enter Contact Information Add Credit Card Set Password In-app Payment Confirmation Receive updates on my Sedan Charge Credit Card Set pickup details Email Receipt to Rider Confirm Pickup Details 13 3 8 5 1 20 20 5 3 WITH STORY POINTS SEDAN BOOKING APP
- 19. Registration Booking Payment Enter Contact Information Add Credit Card Set Password In-app Payment Confirmation Receive updates on my Sedan Charge Credit Card Set pickup details Email Receipt to Rider Confirm Pickup Details 13 3 8 5 1 20 20 5 3 WITH STORY POINTS AND VERSION # v1 v2 Key Story Points SEDAN BOOKING APP
- 21. Story Map Layout
- 22. Registration Booking Payment Enter Contact Information Enter Credit Card Set Password In-app Payment Confirmation Receive updates on my Sedan Charge Credit Card Set pickup details Email Receipt to Rider Confirm Pickup Details SEDAN BOOKING APP
- 23. Registration Enter Contact Information First Name Set Password Enter Credit Card Last Name Email CC # CVV Expiration Date Enter Password SEDAN BOOKING APP
- 25. Account for WHO and WHY
- 26. BREAKOUT
- 27. Story Map your Morning Routine STEPS: 1. List all the things that you do in the morning (one post-it each) 2. Group post-its into categories 3. Arrange as a user story map, fill in gaps or add tasks/subtasks 4. We’ll regroup, and explain our story maps
- 28. DELIVERY
- 29. MVP Highest return on investment versus risk
- 30. Landing Page It looks real You quickly discover it’s not yet built Hopefully you give us your contact info
- 31. Wizard of Oz It looks real Behind the scenes it’s manual But we don’t tell you that
- 32. Concierge It looks real Behind the scenes it’s manual And we let you know it’s manual
- 33. Piecemeal It looks real We use existing tools We may or may not let you know that
- 36. Registration Booking Payment Enter Contact Information Add Credit Card Set Password In-app Payment Confirmation Receive updates on my Sedan Charge Credit Card Set pickup details Email Receipt to Rider Confirm Pickup Details 13 3 8 5 1 20 20 5 3 v1 v2 Key Story Points SEDAN BOOKING APP
- 37. SPRINT THEMES Sprint 1 Sprint 2 Sprint 3 Sprint 4 Team Awesome SEDAN BOOKING APP
- 38. SPRINT THEMES Sprint 1 Sprint 2 Sprint 3 Sprint 4 Team Awesome Registration v1 Booking v1 Add CC, Charge CC Confirm Payment, Email Receipt SEDAN BOOKING APP
- 39. STEP 1: LIST TEAMS & ITERATIONS MULTIPLE TEAMS
- 40. STEP 2: ADD PROJECTS MULTIPLE TEAMS
- 41. STEP 2 CONTINUED MULTIPLE TEAMS
- 42. STEP 2 CONTINUED MULTIPLE TEAMS
- 43. REALITY IS NOT ALWAYS PRETTY MULTIPLE TEAMS
- 45. SHARED UNDERSTANDING IS NOT EASY
- 46. FAST&ITERATIVE > BIG HONKIN’ DOC
- 48. STORY MAP != CONVERSATION != REQUIREMENTS == VISION != USER EXPERIENCE
- 50. Tools Google Drawing CardBoard JIRA – Story Map Plugin StoriesOnBoard FeatureMap SmartView
- 51. Sources & Resources Wikipedia: https://en.wikipedia.org/wiki/Minimum_viable_product https://en.wikipedia.org/wiki/Software_requirements_specification https://en.wikipedia.org/wiki/Traceability_matrix Envato: http://marketblog.envato.com/ux/straightforward-tactics-testing-minimum-viable-products/ The Next Web: http://thenextweb.com/dd/2014/11/12/15-ways-test-minimum-viable-product/ Atlassian University: https://university.atlassian.com/uac/2.0/courses/end-user/jira-agile/v59/rapid-board/rapid-board-scrum/lessonSections/ 01/lessonSectionSteps/0/tourImageBinary/greenhopper59--rapid-board-for-scrum6.png Quick Landing Pages: QuickMVP.com Launchrock.com Recommended Reading List: https://docs.google.com/document/d/1Kfub4LUEEREI9ThHSy045fLF-YWf9fsNYVfloONya2k/edit