Traction story map plan
•Download as PPTX, PDF•
1 like•796 views
This document provides guidance on creating user stories and scenarios to understand user needs. It instructs attendees to: 1. Identify system users and their goals, concerns and typical/exceptional uses through user scenarios. An example scenario for an Acme truck driver is given. 2. Break into groups to develop additional user scenarios, then have groups question each other's scenarios. 3. Extract specific user tasks from the scenarios, like "Receive SMS with order details" or "Verify order availability". 4. Group the user tasks into higher-level user activities to understand the overall user flows. The purpose is to understand customer needs and how users will interact with the system through developing stories and
More Related Content
Similar to Traction story map plan
Similar to Traction story map plan (20)
Traction story map plan
- 3. Who are the customers of the system? • The people who will use this system to gain benefits • E.g., Domestic Carrier • In groups of 3 to 4 - 5 minutes 3
- 4. Thinking through user experience… …using user scenarios "Describes interactions of people and the system in a way we anticipate the people to use the system" 4
- 5. User Scenario • Why do they even have access to the system? (e.g., role in their company, relationship to CTC)Interaction Context • What are they trying to achieve?Goal • What is it they really want to go right, and avoid going wrong?Concerns • What do they do 80% of the time?Typical Use • What do they do 20% of the time? E.g., Edge-cases, rare situations, weird stuff.Exceptions • What affects their decision-making?Influences • What are problems they wouldn’t be surprised to encounter?Typical Problems • What inconveniences do they encounter that they just live with?Pain points 5
- 6. Context: The Acme truck driver is assigned to pick up a shipment which he must do at the pick up time supplied by dispatch. Goal: Receive order through SMS, pick up order at destination. Concerns: 1. SMS provides complete order info, 2. Access to vehicle is available 3. Order is available for pick-up at time stated 4. Wait time is minimal at pick-up location 5. BoL info matches PO Typical Use: 1. Receive SMS with order pick-up details 2. Verify that order will be ready by logging into system and checking pick-up time 3. Accept assignment and notify dispatch by using “Accept Order” feature 4. Pick-up order at destination, notify dispatch through “Notify Dispatch” feature Exceptions: 1. Order is not immediately ready for pick-up when you get there, must wait 2. Order is incomplete, must wait or move on depending on instructions from carrier Influences: Weather, fuel charges, day of week, holiday schedule, weight and volume of order, border wait times, rate per mile Typical Problems: SMS is received too late, SMS contains incorrect Purchase Order ID, driver contention (needs to be resolved via dispatch) Pain Points: 1. Can’t access system via Blackberry 2. Must print Purchase Order when at destination 3. Signing authority needs to be verified every time Example: Acme Truck Driver picks up package 6
- 7. Distribute users and create scenarios • In groups of 3 to 4 - 15 minutes • Every team loses and gains a team member who will poke holes and question the scenarios – 10 minutes 7
- 8. Extract User Tasks From ScenariosTime Tasks 8
- 9. An example to help us out… User Story User Task User Activity Manage Corporate Email View Email Show Inbox Show Single Email Compose Email Create Formatting Toolbar Create Send Extract the User Tasks from the User Scenarios that were created – 15 min 9
- 10. Group the User Tasks into User Activities Time Activities 10
- 11. Time Stories Discussion – Create Stories 11
Editor's Notes
- Get an understanding of the work required on the project, and when it’s required to be doneIdentify stories (big and small) which need to be done – help us estimate a point total for a particular release, or for the whole project
- Think about the end-users of the system, the people who will use the system to benefit
- Now that we have the end users defined, we will soon reflect on their anticipated user experience using user scenariosWe’ll see an example of a scenario and what constitutes a good scenario shortly
- Elements of a scenarioIf you focus on the highlighted parts, you’ll get 80% of a good scenario
- Example scenario taken from a real world project.
- Remember those users we identified, let’s create scenarios for them
- This is the part of the story map we’ll now develop (quick slide)
- We’re now going to develop User Tasks by extracting the “verb parts” from the scenarios we createdHere’s an example of the area we want to focus – User Tasks
- Let’s group the User Tasks we created into User Activities just to help us organizing things a little better.
- Discussion with group to create stories.