The Journey to User Story Map and Roadmaps

DisclaimerNot exhaustive

Not source of absolute truth

Based on my personal perception

Been constantly improved

Starting before the beginning

Getting speed

Vision(OKR)

1st Iteration: Business Model and Hypotheses

Finding the risky stuff

Design Sprint

By then, you have

A high level customer journey

Tested prototypes

Insights in what customers want

Now it’s time to...

(OKR)

User Story Mapping

Reviewing

1. product / market fit.

2. quickly build your idea

3. release, manage and scale up your idea.

1. Lean Startup and Design Thinking

2. Some form of Agile Software

Development for building your idea

3. DevOps for releasing and managing it in

production.

Blog “extreme uncertainty” http://sumo.ly/kF22

Reviewing

1. product / market fit.

2. quickly build your idea

3. release, manage and scale up your idea.

1. Lean Startup and Design Thinking

2. Some form of Agile Software

Development for building your idea

3. DevOps for releasing and managing it in

production.

Blog “extreme uncertainty” http://sumo.ly/kF22

Reviewing

1. product / market fit.

2. quickly build your idea

3. release, manage and scale up your idea.

1. Lean Startup and Design Thinking

2. Some form of Agile Software

Development for building your idea

3. DevOps for releasing and managing it in

production.

Blog “extreme uncertainty” http://sumo.ly/kF22

Wikipedia

Agile practices

Agile development is supported by a bundle of concrete

practices, covering areas like requirements, design, modelling, coding, testing, project

management, process, quality, etc. Some notable agile practices include:

...

User Story Mappinghttps://en.wikipedia.org/wiki/Agile_software_development#Agile_methods

Meet Jeff Patton

https://www.amazon.de/User-Story-Mapping-Discover-Product/dp/1491904909

USM Example - product improvement

Steps

Details(Epics)

Themes

Outcome/Target

Release

Meet my USM

How to start ?

“Telling Stories, Not Writing Stories” - Jeff Patton

Radical Agility

KPIs - the compass

If we will make progress towards the product goal, how we will know it ?

Cards, Conversation, Confirmation

Goal clear after discovery and tests

1)Title, Who, What, Why (As... I want... So that...)

Talk to understand details

2)Additional details, sketches, etc.

3)Acceptance criterias (how do we know that the story is done)

Building the User Story Map

Silently write down the user tasks based on the current common understanding and stick on the wall.

...Remove duplicates

...Group tasks

...Name groups

A B C

...Arrange left to right

A B C

...Fill the gaps

A B CA1 D

Add details

- Iterate

- Show to more people

- Improve itA B CA1 D

BACKLOG

Prioritise Outcomes

A B CA1 D

21 3

Prioritise Backlog

A B CA1 D

2

1

3

BA

CK

LOG

Estimations based on team’s velocity

A B CA1 D

2

1

3

BA

CK

LOG

3 weeks

4 weeks

2 weeks

Any question?