Download - Effects driven Scrum development using Business impact maps

Transcript
Page 1: Effects driven Scrum development using Business impact maps
Page 2: Effects driven Scrum development using Business impact maps

2

Introduction

Sara LerénUser Experience Specialist

[email protected]

Agile UX Sweden

@HeedTheNeed

Page 3: Effects driven Scrum development using Business impact maps

3

Agenda

Effects-driven Scrum development using Business Impact Maps

How is value created?How do people express their needs?Visualizing the business needs using Business impact mapsUsing Business impact maps in Scrum

Page 4: Effects driven Scrum development using Business impact maps

Value Creation

How do you create value?

Page 5: Effects driven Scrum development using Business impact maps

Missed mark – Airport VIP lounges

Page 6: Effects driven Scrum development using Business impact maps

6

Agenda

Effects-driven Scrum development using Business Impact Maps

How is value created?How do people express their needs?Visualizing the business needs using Business impact mapsUsing Business impact maps in Scrum

Page 7: Effects driven Scrum development using Business impact maps

Value Creation“If I’d asked my customers what they wanted, they would have said, ‘A faster horse!’”

Henry Ford

Page 8: Effects driven Scrum development using Business impact maps

How do people express their needs?

Explicit needs

Visible needs

Latent needs

Page 9: Effects driven Scrum development using Business impact maps

Gemba

Gemba, “the real place”

Page 10: Effects driven Scrum development using Business impact maps

10

Agenda

Effects-driven Scrum development using Business Impact Maps

How is value created?How do people express their needs?Visualizing the business needs using Business impact mapsUsing Business impact maps in Scrum

Page 11: Effects driven Scrum development using Business impact maps

Gemba

What is a Business Impact Map?

A way of visualizing the Business needs and the Effects required to satisfy the needs

Page 12: Effects driven Scrum development using Business impact maps

Gemba

The structure of the Business Impact Map

Page 13: Effects driven Scrum development using Business impact maps

Why Impact Mapping?

Why Business Impact Mapping?

Page 14: Effects driven Scrum development using Business impact maps

Why Impact Mapping?

Techies vs. Techies

Page 15: Effects driven Scrum development using Business impact maps

Why Impact Mapping?

Business people vs. Techies

Page 16: Effects driven Scrum development using Business impact maps

Business Impact Maps tell stories

Source: Allen R. Braun, M.D, National Institute on Deafness and Other Communication Disorders

Reading Words

Reading Sentences

Reading Stories

Page 17: Effects driven Scrum development using Business impact maps

17

Agenda

Effects-driven Scrum development using Business Impact Maps

How is value created?How do people express their needs?Visualizing the business needs using Business impact mapsUsing Business impact maps in Scrum

Page 18: Effects driven Scrum development using Business impact maps

GembaSprint 0 –

Time to create the Business Impact Map

Page 19: Effects driven Scrum development using Business impact maps

Gemba

User group analysis and prioritization

Page 20: Effects driven Scrum development using Business impact maps

Missed mark – not knowing your market

Page 21: Effects driven Scrum development using Business impact maps

Gemba

Defining effect goals

Page 22: Effects driven Scrum development using Business impact maps

Planning sprint 1 –The Business Impact Map works as a high-level backlog and

facilitates prioritization

Page 23: Effects driven Scrum development using Business impact maps

User stories are easily extracted from the Business Impact Map

As a [user group] I want [need] so that [effect]

Example:As a family traveller I want to keep my children

entertained so that I can keep calm

Page 24: Effects driven Scrum development using Business impact maps

Sprint demo –The effect goals help to focus on what’s important

Page 25: Effects driven Scrum development using Business impact maps

Focusing on the desired effects

Page 26: Effects driven Scrum development using Business impact maps

Evaluating proposed solutions

Page 27: Effects driven Scrum development using Business impact maps

Final sprint –Final evaluation of effect goals

Page 28: Effects driven Scrum development using Business impact maps

Value Creation

Have you created value?

Page 29: Effects driven Scrum development using Business impact maps

29

The End

Thank you!

Want to get in touch?

[email protected]

Agile UX Sweden

@HeedTheNeed