1. 29/11/2017

2. All rights reserved to Sapir Consulting
29/11/2017
All rights reserved to Sapir Consulting

3. 29/11/2017
User Story Mapping
A user story map arranges user stories into a useful model to help understand the functionality of the system, identify holes and omissions in your backlog, and effectively plan holistic releases that deliver value to users and business with each release
Around flipcharts in pairs – 25 minutes
Outcomes
Expectations
What we already know

4. Objectives, Expectations, Overview
29/11/2017
Objectives, Expectations, Overview
Objectives
Learn by example how to lead a User Story Mapping session
My expected learning outcomes
What do I already know about the topic
Around flipcharts in pairs – 25 minutes
Outcomes
Expectations
What we already know

5. Michael Nir President @ Sapir Consulting US
Transformation Inspiration Expert, Lean Agile Coach; empowers organizations to deliver results
Author of 10 bestseller business books

6. What Do I Know about Story Mapping
29/11/2017
What Do I Know about Story Mapping
Have you used the process before?
Discuss with a partner
Reflect – what were the pros and cons?

7. Insights from Jeff Patton
29/11/2017
Insights from Jeff Patton
Story mapping keeps us focused on users and their experience, and the result is a better conversation, and ultimately a better product
There’s always more to build than we have time or resources to build – always
Stories get their name from how they should be used, not what should be written

8. Creating your first map
29/11/2017
Creating your first map
Take a minute and think back on what you did first, when you woke up this morning – write it on a sticky – peel and place in front of you
What was the next thing? – write it on a sticky – peel and place in front of you
Keep going until you’ve gotten ready for work and left your house
Following Patton – User Story Mapping

9. Tasks are what we do These are User Tasks
29/11/2017
Tasks are what we do
A STEP AT A TIME
These are User Tasks
They start with a verb – mostly
Do you have tasks? More? Less?
Are they different from the person next to you?
User tasks are the basic building blocks of a story map
Following Patton – User Story Mapping

10. 29/11/2017
Organize
A STEP AT A TIME
Left to right flow: first I did this and then this…Narrative flow – story telling order
Silently! Create one map with the people at your table
Following Patton – User Story Mapping

11. 29/11/2017
Level of Detail
Tasks are like rocks that are different in size (sometimes)
Follow Goal level concept – Alistair Cockburn – sea-level task:
Sea level – we expect to complete before intentionally stopping to do something else
Use the goal-level concept to help you aggregate small tasks or decompose large ones
Take a shower – sea level
Because you don’t go half way through the shower and think: man this shower is dragging on. I think I’ll grab a cup of coffee and finish this shower later.
Take shower breaks into smaller subtasks – wash hair – below the ocean – use fish
Summary-level task – showering, brushing teeth, shaving – maybe getting cleaned up?
Following Patton – User Story Mapping

12. Explore alternative stories
29/11/2017
Explore alternative stories
Think about what you did yesterday morning…if there are different things – add them
Think of a morning that things went wrong and an ideal morning
Maintain the flow
Details, alternatives, variations and exceptions fill in the body of the map
Following Patton – User Story Mapping

13. Distill Your Map to Make a Backbone
29/11/2017
Distill Your Map to Make a Backbone
Cluster stories that seem to go together
Place a different colored sticky above and write a short verb phrase that distills the stories clustered
High goal-level tasks are called – Activities
They also form a narrative at a higher level
Activities aggregate tasks directed at a common goal – they form the backbone of a story map
Following Patton – User Story Mapping

14. Slice by Specific Outcomes
29/11/2017
Slice by Specific Outcomes
A minimal viable product is the smallest thing we could create or do to prove or disprove an assumption
Our job is not to build more software faster, it is to maximize the outcome and impact we get from what we chose to build
The alarm didn’t go off ro you forgot to set it..
Select other goals:
Go out for two weeks vacation
Have the luxurious morning ever
Narrative stays he same – you’ll need to move tasks in and out
Following Patton – User Story Mapping

15. Slice by Specific Outcomes
29/11/2017
Slice by Specific Outcomes
Write a desired outcome on a different color sticky and place to the left of the map near the top row
For example: “get out the door in a few minutes”
Move all the tasks that you wouldn’t complete to reach the goal – below the goal slice. Keep the Activities on top
Use slices to identify all the tasks and details relevant to a specific outcome
The alarm didn’t go off ro you forgot to set it..
Select other goals:
Go out for two weeks vacation
Have the luxurious morning ever
Narrative stays he same – you’ll need to move tasks in and out
Following Patton – User Story Mapping

16. Recap Tasks are short verb phrases the describe what people do;
29/11/2017
Recap
Tasks are short verb phrases the describe what people do;
Tasks have different goal levels;
Tasks in a map are arranged in a left to right narrative flow;
The depth of a map contains variations and alternative tasks;
Tasks are organized by activities across the top of the map;
Activities form the backbone of the map;
you can slice the map to identify the tasks that you’ll need to reach a specific outcome – a slice can be used for releases, MVPs etc
Add one of the questions from back of the room

17. Act Now – User Story Mapping
29/11/2017
Act Now – User Story Mapping
Reflect with a partner: how can you use Story mapping at your work environment
Identify 2-3 actionable items as take-aways
Start TODAY

18. 29/11/2017
Thank you! I wish you success in mapping a user journey into stories and product backlogs