Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a User Story Mapping - WHY and HOW, a handson workshop
Similar a User Story Mapping - WHY and HOW, a handson workshop (20)
Más de bhumika2108
Más de bhumika2108 (19)
Último
Último (20)
User Story Mapping - WHY and HOW, a handson workshop
- 2. ABOUT US #agileenthusiast #keentolearnmoreaboutagile #alwaysreadytolearn #happytocoach #softwaredevelopmentlead #industrymentoratmonash #collaboration sghara@gmail.com SHOM (Soumendu Ghara) Development Lead @ MYOB #industrymentoratmonash #collaboration #testautomation #qualityanalysisovertesting #keentolearn bhumikaiyengar@gmail.com Bhumika Srinivas Sr QA @ MYOB
- 3. 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
- 4. Big Picture High Level Goal
- 5. Discovery
- 9. Feedback
- 10. Personas
- 11. MVP
- 12. 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
- 13. Discovering our users’ world Approach 1: Identify high level activities first and then refine details
- 14. Discovering our users’ world Approach 2: Discover detailed activities and group them in high level activities
- 15. Visualise what we have discovered Approach 2: Group all activities under the high level activities
- 16. Typical Tasks Alternate Tasks Error Tasks Refine & Prioritise to maximise value
- 17. 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’
- 18. 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
- 19. 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.
- 20. 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..
- 21. Q & A
- 22. All the images in this presentation are courtesy: https://unsplash.com/ and https://pixabay.com/