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.

User Story Mapping - WHY and HOW, a handson workshop


Published on

* What is the philosophy behind story mapping, why we do it?
* Understand how to effectively story map is a crucial capability for an agile team
* Helps teams learn collaboration, share and prioritise quickly and efficiently.

Published in: Software
  • My brother found Custom Writing Service ⇒ ⇐ and ordered a couple of works. Their customer service is outstanding, never left a query unanswered.
    Are you sure you want to  Yes  No
    Your message goes here
  • I’ve personally never heard of companies who can produce a paper for you until word got around among my college groupmates. My professor asked me to write a research paper based on a field I have no idea about. My research skills are also very poor. So, I thought I’d give it a try. I chose a writer who matched my writing style and fulfilled every requirement I proposed. I turned my paper in and I actually got a good grade. I highly recommend ⇒ ⇐
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

User Story Mapping - WHY and HOW, a handson workshop

  1. 1. ABOUT US #agileenthusiast #keentolearnmoreaboutagile #alwaysreadytolearn #happytocoach #softwaredevelopmentlead #industrymentoratmonash #collaboration SHOM (Soumendu Ghara) Development Lead @ MYOB #industrymentoratmonash #collaboration #testautomation #qualityanalysisovertesting #keentolearn Bhumika Srinivas Sr QA @ MYOB
  2. 2. PRESENTATION 10 mins INTRO to workshop 5 mins WORKSHOP 20 mins SUMMARISE and Q&A 5 mins © Soumendu Ghara User Story Mapping - WHY and HOW
  3. 3. Big Picture High Level Goal
  4. 4. Discovery
  5. 5. Prioritisation & Refinement
  6. 6. Prioritisation Refinement Discovery
  7. 7. Alternatives Error Conditions
  8. 8. Feedback
  9. 9. Personas
  10. 10. MVP
  11. 11. STORY MAPPING Personas Problem Business Solution Technical Solution Context Dependency Priority Delivery Feedback Story mapping is a collaborative practice to visualise the product backlog through the user’s lens - 30 July Soumendu Ghara
  12. 12. Discovering our users’ world Approach 1: Identify high level activities first and then refine details
  13. 13. Discovering our users’ world Approach 2: Discover detailed activities and group them in high level activities
  14. 14. Visualise what we have discovered Approach 2: Group all activities under the high level activities
  15. 15. Typical Tasks Alternate Tasks Error Tasks Refine & Prioritise to maximise value
  16. 16. Find the product Get it Return/ exchange Select and place order Input the product Search the product View product list See the specific prod Filter the list of products See product details Compare products select multiple products Compare selected prod Select the product Select multiple prod Know the total Get it delivered Pick up Pay for the product Able to pay – CC, Debit Get a receipt Able to pay – Paypal Save card for future Save card for future Able to return Able to exchange Know cost of delivery Delivery time for delivery Delivery time for pickup Customer Persona identification and typical activities List a product Receive the order Serve the order Post sales support Seller We will try to build an e-comm website that sells ‘products’
  17. 17. 1. Divide yourselves into groups of 5-6 people. 2. Look at a familiar use case scenario. 3. Identify some of the relevant personas. 4. Discover the high level activities in a sequence which tells the users’ story. 5. Breakdown into detailed activities. 6. Prioritise to define the MVP. 20 mins Lets work together
  18. 18. Problem Statement. Your organisation owns an intranet portal whose primary goal is to improve employee engagement across the business and develop a stronger company identity. New Proposed Feature: Enable employees to search for co-workers and view their details to enable collaboration within teams and share information throughout the organization.
  19. 19. 1 Personas 3 Refine 4 Prioritise MVP 2 Big Picture Whose problems are we solving ? Do we know the high level problems, the user’s world, a typical day for the user ? Breakdown the high- level problems into smaller ones Form the leanest product approach keeping in mind – what will bring most value with least effort Is this good enough for us to trial the product and get feedback ? 5 MVP To Summarise..
  20. 20. Q & A
  21. 21. All the images in this presentation are courtesy: and