Dealing with a massive backlog

Who we are?

1,700 teammembers

>60 na0onali0es

44 markets

15 offices

12 countries

1 globalcompany

5 leading brands

2000 | Barcelona

1997 | Paris

2001 | Stockholm

2001 | multilocation

2001 | multilocation

300 x 10 = 3000

2014

ESF

4-5 months average

Proposal &

business case

Business case review

Top management approval

WHY WHAT HOW WHEN HOW MUCH ?

ESP and Transformation Scout team WHY? Transformation Scouting period

2015

User Journey Brainstorming

3 weeks

Size effort

Prioritization

US split

WHAT? Building a backlog from scratch

OPEN REPLENISHMENT MEETINGS RISK PROFILE IS ALSO USEFUL TO PRIOR

Upstream user story mapping view

Analysis WIP Done

Profitable content

User experience

POD Portfolio Matching Features & Team objectives

A

D

J E

F

I

O

L

H

M

N

C

G

B

K

WIP Analysis Done

Our first Risk Profile

Everything is around a BALANCED PORTFOLIO !!!

13

Is your backlog balanced?

▪  Are we managing housekeeping tasks as well as differentiators?

▪  Are we targeting low-effort incremental gains and higher impact

projects too? ▪  Are the tactical projects balanced with feature developments that

will help us catch up with competitors? etc

14

Our Risk Profile Today

TECHNICAL/PLATFORMRISK

SevereEBITDAimpactMajorrevenueimpact

Discre8onaryrevenueimpact

Intangible

None

Wedidbefore

M

L

Differen8ator

Costreducer

Catch-up Op8miza8on

MARKETRELEVANCE/UX

DELAYIMPACT

EFFORTS

L

M

Unknown

Low

Medium

HighCUSTOMERVALUE

XL

Effort Days S 2

M 4

L 7

XL 14

?

?

OPEN REPLENISHMENT MEETINGS

UNCERTAINTY!

17

• Hypothesis • Risk profile • Data • Opportunity • KPIs • Benchmarking • User research

• Prototyping • Validation • Risk profile • MVP

• Mockups • US split • TA

DESIGN & TECHNICAL EXECUTION

DEVELOPMENT LIVE FOR USERS VALIDATION OPTIONS DISCOVERY

UPSTREAM FLOW

DISCOVER DELIVER

WIP 6

WIP ongoing WIP ongoing

1. Organisational Chart

ASK USERS & VALIDATE !!!

Quantitative Analysis -Online Exit Survey

Question A

Question B

Question C

Question D

User Problem

How to cover User needs?

11

25

30

10

Delighter

Pain point

Pain point

Performance

Basic Need

Answer1

Answer2

2

Answer1

Answer2

Answer1

Answer1

Answer2

5

17

A)

Is hypothesis driven development for Startups only? Risky feature

Qualitative data

Quantitative data

EXPERIMENT

HIGH RISK

Com

mitm

ent p

oint

Building Business

Case

How

B)

Discard

Iterate

LOW Qualitative

data

QUANTITATIVE: EXPERIMENT in

user real environment

LOW RISK

Com

mitm

ent p

oint

Low Risk feature

Visualizing capacity & type of work

WHEN?

Discover, experiment and learn faster