Story Mappin'

Not all 'story' maps are built the same... Let's build better product story map...

Transcript

1. STORY MAPPIN’ Step on transporter pad Crack joke about molecules Slap Bones on the Back Laugh Tell Scotty to Energize Raise Eyebrow Glare at Kirk Digitize Molecules Materialize on planet surface Send data beam to planet image source: http://www.adammunoaart.com/2012/04/lessons-from-kirk.html
2. story mapping... “I was introduced to stories in 2000... and since then it’s gone HORRIBLY SIDEWAYS...!” - Jeff Patton
3. Maps of all shapes and sizes • Journey Map • Empathy Map • Feature Map • Story Map All are currently being used in some form or fashion, most are feature maps. So let’s build better Story Maps!
4. Journey Map “list of tasks that a user is currently doing” Similar to a Story Map, but used to illustrate and understand how a user is currently solving their problem. Customer A Customer B Customer C
5. Empathy Map Empathy maps can be used whenever you find a need to immerse yourself in a user’s environment. Image Source: http://www.bigvisible.com/2012/06/what-is-an-empathy-map/
6. Feature Map “feature map is basically a dumb list of stuff we need to build” -Jeff Patton Product Feature Map Holistic view, grouped by ‘WHY’
7. What is a Story Map? "Story maps are really about discussion, conversations, breaking big ideas into granular details" - Jeff Patton
8. First, What is a Story? A story is a named item that we might build in our software • It names what we might build • It tries to avoid saying how User Stories act as the boundary to facilitate conversation between many people (The User, PO, Dev, UX, QA)
9. What is a Story? cont. • Stories mean different things to different people • Stories need different details to support different people's work • Stories have different natural sizes depending on who your talking to Stories "... are weakly structured in common use, and become strongly structured in individual use."
10. So how do we build Stories? Keep the language simple "Express stories in a language most people can understand" Build stories with different sizes. Your backlog should have a variety of related stories to drive conversation about what your building Don't sweat the details Details should be discussed in other pertinent meetings, where they are useful.
11. Sample Stories User requests data Email Recieved Login to App Email Generated User inputs data into cells User clicks Submit button Click Browse Select File Click Link Confirmation Dialogue
12. The Story Map Product Story Map
13. The Backbone Latitude: time based, the users perspective Longitude: priority, our perspective PRIORITY TIME
14. Anatomy of a Story Map Big capabilities User's steps - smaller steps - UI details - technical details/steps MVP/Release levels
15. Where do I start? The ‘Walking Skeleton’ ‘the least number of necessary tasks across the full span of user experience’ Start at the highest level necessary and backfill stories Separate out User Tasks/Actions & System Tasks Revist the map constantly Review the Map with others, poke holes in the flow, identify pain points and iterate based on the conversation.
16. final thoughts • Build a physical map when possible • Start with the ‘Walking Skeleton’ • Only be as specific as you need to • Focus on the MVP’s or MVR’s (Minimum Viable Release) • Improve holistically over time as you gain product knowledge Alway refer back to the map!
17. Go forth and Prosper! Questions?