impact mapping: business success in software development

20
1 Tél : +33 (0)1 58 56 10 00 Fax : +33 (0)1 58 56 10 01 www.octo.com © OCTO 2013 50, avenue des Champs-Elysées 75008 Paris - FRANCE Sergey Larionov, David Friquet 11 March 2014 Impact mapping

Upload: sergeyla

Post on 10-May-2015

2.298 views

Category:

Business


0 download

DESCRIPTION

OCTO Technology vision of Impact Mapping. Full text of the article: http://blog.octo.com/en/impact-mapping-business-success-in-software-development/ Based on: - the book Impact Mapping of Gojko Adzic, the author of the method, - presentation by Gojko Adzic, - workshop Product Owner Survival Camp London 2013, - interview with Gojko Adzic at OCTO Technology.

TRANSCRIPT

Page 1: Impact mapping: business success in software development

1

Tél : +33 (0)1 58 56 10 00Fax : +33 (0)1 58 56 10 01www.octo.com© OCTO 2013

50, avenue des Champs-Elysées75008 Paris - FRANCE

Sergey Larionov, David Friquet

11 March 2014

Impact mapping

Page 2: Impact mapping: business success in software development

2

What is it?

Page 3: Impact mapping: business success in software development

3

Impact mapping

Impact mapping is a visual strategic planning technique that helps teams to align their activities with overall business objectives and make a better decision

Page 4: Impact mapping: business success in software development

4

Why do I need it?

Page 5: Impact mapping: business success in software development

5

Benefits

Impact your business, not just ship software

More value, less software

Facilitate collaboration and interaction

Align technical experts and managers

Adapt quickly to changing market needs

Make a better decision

Page 6: Impact mapping: business success in software development

6

How does it work?

Page 7: Impact mapping: business success in software development

7

Steps

Page 8: Impact mapping: business success in software development

8

Preparation

US doesn’t tell you how much money we can get from it.To know what is a real value/priority there are few questions we need to ask:

Why are we doing this? (goal)

Who we want to help? Who are our customers/users? (actors)

What do these people want? (impacts)

How can we help them achieve that? (deliverables)

Page 9: Impact mapping: business success in software development

9

Mapping

Make it visual !

Page 10: Impact mapping: business success in software development

10

Why? Who? How? What? – WTF…

Page 11: Impact mapping: business success in software development

11

Win the race

Page 12: Impact mapping: business success in software development

12

More players

Page 13: Impact mapping: business success in software development

13

Impacts?

Page 14: Impact mapping: business success in software development

14

Few secrets

Page 15: Impact mapping: business success in software development

15

SMART goal

Specific – target a specific area for improvement.

Measurable – quantify or at least suggest an indicator of progress.

Assignable – specify who will do it.

Realistic – what results can realistically be achieved, given available resources.

Time-related – specify when the result(s) can be achieved.

Page 16: Impact mapping: business success in software development

16

Measurements

More profit… How much more is more?

Page 17: Impact mapping: business success in software development

17

Design thinking

Alternatives Right decision

Page 18: Impact mapping: business success in software development

18

Impact mapping User Story

Big picture:Save money/Increase profit.

How somebody’s work change the company profit.

Changing somebody’s work/behaviour.Is this report going to help you to do your job faster.

Page 19: Impact mapping: business success in software development

19

Sources

1. Make Impacts Not Software. Gojko Adzic, Agile Adria 2013.2. Impact Mapping. Gojko Adzic, 2012.3. Product Owner Survival Camp. Workshop with Gojko Adzic, London 2014.4. Adapt: Why Success Always Starts with Failure, Tim Harford, 2011.5. Les Géants du Web : Culture - Pratiques - Architecture. OCTO Technology, 2012.6. Effect Mapping at the Nordstrom Innovation Lab. Olaf Lewitz, 2012.

Page 20: Impact mapping: business success in software development

20

ANY QUESTIONS ?JUST SEND ME AN EMAIL !

[email protected]