Workshop: User story mapping by Nermina Durmic
3 likes423 views
The document outlines a user story mapping process by Nermina Durmic, detailing steps from defining product goals and user flows to feature prioritization and release planning. It emphasizes collaboration through silent brainstorming and organizes tasks into a structured map to clarify product scope and development priorities. The methodology also incorporates examples, personas, and prioritization techniques like the MoSCoW method for effective planning.
Workshop: User story mapping by Nermina Durmic
- 1. User Story Mapping Nermina Durmic
- 2. NERMINA DURMIĆ Product Owner Assistant Professor nermina@agile.ba linkedin.com/in/nerminadurmic researchgate.net/profile/Nermina_Durmic
- 4. User story mapping - goals • Innovation through silent brainstorming • Big picture • Product Scope • Release planning Map of: WHAT? HOW? WHEN?
- 5. Step 1 – Which product are we building? • Define the main product goal • Which problems is it solving? • Potential users?
- 6. Step 2 – Define the basic user flow • Each team member, in silence, makes set of user tasks of the product – one task per sticky note. • Basic tasks user can do using the product in chronological order (horizontal line) • Every user task starts with a verb (e.g. Add a friend) • Walking skeleton
- 7. Step 2 – Examples Facebook Create account - Login/Logout - Add profile details - Upload profile photo – Upload photos - Create a text post – View user profile – Add a friend – News feed Booking.com Add hotel description and pictures – Type in destination and dates – Matching algorithm – Display results – Hotel details page – Hotel availability – Book a hotel – Process the payment
- 8. Step 3 - Walking Skeleton • Each team member reads their tasks out loud • Throw away duplicates • Finalize the walking skeleton
- 9. Step 4 – Group your user tasks • Group similar tasks in the skeleton horizontally • Every group gets a name – use sticky note in another color • These are big activities of our product – modules • The Backbone of the story map • Used to keep the map organized
- 10. Step 5 – Adding more features • Vertically, under each task list down features that increase sophistication Example: TASK: Add a friend Remove a friend Delete friend request Block user
- 11. Step 5 – Adding more features
- 12. Step 5 – Personas concept helps Farah Primary persona 8 years old, likes music and dancing, She takes ballet classes Uses iPad She wants to enjoy music and dancing Emina Farah’s mother, used to teach ballet She wants her daughter to enjoy fun and educational game
- 13. Step 6 – Feature prioritization • Chose two dimensions to value features against: Business value, User impact, Risk of not adding a feature, Dependencies, Knowledge, Uncertainty… • For both dimensions, grade each feature in the map with 1-5, 5=highest priority • Product of these values represents the final priority of the feature • We don’t prioritize activities in the Backbone.
- 14. Step 6 - Feature prioritization • Order features in vertical lines with respect to their priority (highest to the top).
- 15. Step 7 – Release planning • MoSCoW technique Example: Must have (e.g. 25, 20, 16), Should have (e.g. 15, 12, 10), Could have (e.g. 9, 8, 6, 5), Won’t have (e.g. 4, 3, 2, 1).