1. The document discusses how to deal with a massive backlog of 1,700 team members across 15 offices and 12 countries. 2. It provides information on their 5 leading brands and how they have been establishing new locations since 2000. 3. The key aspects of managing the backlog are discussed, including prioritizing projects based on their potential business impact, technical risk, customer value, and effort required. Maintaining a balanced portfolio of projects is emphasized.

1. Dealing with a massive
backlog

2. Who we are?
1,700 team members
>60 na0onali0es
44 markets
15 offices
12 countries
1 global company

3. 5 leading brands
2000 | Barcelona
1997 | Paris
2001 | Stockholm
2001 | multilocation
2001 | multilocation

4. 300 x 10 = 3000

5. 2014
ESF
4-5
months
average
Proposal &
business case
Business case
review
Top management
approval

6. WHY
WHAT
HOW
WHEN
HOW MUCH
?

7. ESP and Transformation Scout teamWHY?
Transformation
Scouting period

8. 2015
User Journey
Brainstorming
3 weeks
Size effort
Prioritization
US split
WHAT? Building a
backlog from
scratch

9. OPEN REPLENISHMENT MEETINGS
RISK PROFILE IS ALSO USEFUL TO PRIOR
Upstream user story mapping view

10. 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
WIPAnalysis Done

11. Our first Risk Profile

12. Everything is around a
BALANCED PORTFOLIO !!!

13. 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. 14
Our Risk Profile Today
TECHNICAL/PLATFORM
RISK
Severe EBITDA impact
Major revenue impact
Discre8onary revenue impact
Intangible
None
We did
before
M
L
Differen8ator
Cost
reducer
Catch-up Op8miza8on
MARKET
RELEVANCE / UX
DELAY IMPACT
EFFORT S
L
M
Unknown
Low
Medium
High CUSTOMER
VALUE
XL
Effort Days
S 2
M 4
L 7
XL 14
?
?

15. OPEN REPLENISHMENT MEETINGS

16. UNCERTAINTY!

17. 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 USERSVALIDATIONOPTIONS
DISCOVERY
UPSTREAM FLOW
DISCOVER DELIVER
WIP 6
WIP
ongoingWIP ongoing

18. 1. Organisational Chart
ASK USERS &
VALIDATE !!!

19. 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
Answer
1
Answer
2
2
Answer
1
Answer
2
Answer
1
Answer
1
Answer
2
5
17

20. A)
Is hypothesis driven development for Startups only?
Risky feature
Qualitative
data
Quantitative
data
EXPERIMENT
HIGH RISK
Commitmentpoint
Building
Business
Case
How
B)

21. Discard
Iterate
LOW
Qualitative
data
QUANTITATIVE:
EXPERIMENT in
user real
environment
LOW RISK
Commitmentpoint
Low Risk feature

22. Visualizing capacity
& type of work

24. WHEN?

25. Discover, experiment and
learn faster