This document summarizes ImmobilienScout24's adoption of Scrum. It describes how ImmobilienScout24 transitioned from waterfall development to adopting Scrum across the entire organization from 2008-2009. Key aspects included training managers and teams, starting with a pilot Scrum team in 2008, and completing company-wide Scrum adoption in 2009 with 12 Scrum teams.

1. www.immobilienscout24.de
SCRUM at
ImmobilienScout GmbH
Munich | 06.05.2009 | Boris Gloger / Oliver Zeiler

2. ImmobilienScout GmbH
ImmobilienScout24 is the leading
real-estate portal in the German
speaking countries. With our more
than 450 employees in Berlin we
hope to offer the best service to all
our customers:
>3.7 Mio Unique Users /month
> 1 Billion Page Impressions /month
> 150 Mio virtual real-estate visits /
month (Viewing of exposé)
> 1.2 Mio real-estate objects /month
> 95.000 real-estate providers /
month
Seite 2 | SCRUM at ImmobilienScout GmbH | Boris Gloger / Oliver Zeiler

3. 2002 First Scrum Team
2003 Certified ScrumMaster, 10 / 25 people are today
ScrumCoaches
2004 1st Certified Scrum Trainer in Europe
2005 First Large Scrum in Germany
2006 First Very Large Scrum in Europe
2007 Start of Scrum in Brazil
2008 Change of Organizational Structures in larger Companies
2009 Running the whole Product Development using Scrum -
Change of the whole organization
f.e. ImmobilienScout24, Nokia, Web.de, StudiVZ,
Siemens PSE, XING, und und und und und
2500 CSM und 200 CSPOS trained

4. Facts, facts, facts (1/3)
One of Germany’s largest internet-portals
 Approx. 130 internal IT-employees, 3 external development teams
 More than 1.5 Mio LoC in Java, same amount in php, Perl, Ruby,…
 Approx. 10.000 IS24-WebPages
 Approx. 15 major- and 70 service releases per year
 2 external data-centers, 100% redundant in Hamburg and Berlin
 Approx. 600 virtual, 250 physical servers
 Portal-availability of currently 99.95% (last three months)
 Page-performance „best in class“
Seite 3 | SCRUM at ImmobilienScout GmbH | Boris Gloger / Oliver Zeiler

5. Facts, facts, facts (2/3)
History Waterfall-development with non-prioritized
projects and unfocussed development
02/2008 2 product-managers and 2 IT-team leads
attended a Certified Scrum-Master training
06/2008 Recommendation of the CSMs regarding a
Scrum-introduction at IS24
08/2008 Combined CSM- and CSPO-training for nearly
all managers and team leads (36 MA)
09/2008 Start of the first IS24 Scrum-team
(2week- sprints until 03/2008, now 3week
sprints)
05/2009 Company-wide Scrum-introduction completed
Seite 4 | SCRUM at ImmobilienScout GmbH | Boris Gloger / Oliver Zeiler

6. Facts, facts, facts (3/3)
SCRUM Roll-out (9 Feature-Teams + 3 SYS-Teams)
108 Stories in 2009
Sep Oct Nov Dec Jan Feb Mar Apr Mai Jun Jul Aug
Task (till end of April)
Sprint 1 – PMI 1
Sprint 4 – PMI 3
Sprint 7 – PMI-2, BBP
Sprint 13 – OC1, OC2a/b
Sprint 15 – PMI 4
Sprint 17 – OM
Seite 5 | SCRUM at ImmobilienScout GmbH | Boris Gloger / Oliver Zeiler

7. CHECK it - Daily Scrum
HOW to do - Sprint Planning 2
WHAT to do - Sprint Planning 1
The
Scrum
Analyse
PB
Flow
Tactical
©
2009
Level
Sprint # 1 Sprint # 2 Sprint # 3 Sprint # 4
9:00
....... ....... ....... .......
Sprint Planning 1
Sprint Planning 1
Sprint Planning 1
Sprint Planning 1
CU
STO MER
Do your Daily Scrum every day! Do your Daily Scrum every day! Do your Daily Scrum every day!
M
ANAGER
Product Idea
Estimation Meeting
12:00
Review
Review
Review
Sprint
Sprint
Sprint
Sprint
Sprint Planning 2
Sprint Planning 2
Sprint Planning 2
Sprint Planning 2
VISION spective
spective
spective
Retro-
Retro-
Retro-
Retro-
PR
ER
Sprint
Sprint
Sprint
Sprint
O N
DU
CT OW
SC
R
E
R
Version 1.2
T
UM
MAS
18:00
TEAM
Day 1 Release
Product Backlog
Estimation
Estimation
Estimation
Estimation
Estimation
Estimation
Estimation
Estimation
prioritized
Meeting
Meeting
Meeting
Meeting
Meeting
Meeting
Meeting
Meeting
PB PB PB PB PB PB PB
1
100
20
Under ?
52
Strategic
stand Planning
Poker
Play!
CU CU
13 30
8
40
M M
STO MER STO MER
ANAGER ANAGER
USER USER
Level
3
Releaseplan Releaseplan Update 5
20
8
8
13
version 0.0 version 1.0 version 1.3 version 2.0 version 0.0 version 1.0 version 1.2 version 2.0
5
TEAM
SIZE it - Estimation Meeting

8. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO

9. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
Training

10. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
Training

11. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
Backlog
Training Prep

12. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
Backlog
Training Prep
Estim.

13. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
Backlog
Training Prep
Estim.
Prio

14. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
Backlog
Training Prep
Estim.
Prio

15. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
Backlog
Training Prep
Estim.
SP 2
Prio

16. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
Backlog
Training Prep
Backlog
Prep
Estim.
SP 2
Prio

17. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
Backlog
Training Prep
Backlog
Prep
Estim.
SP 2
Estim.
Prio

18. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
Backlog
Training Prep
Backlog
Rev
Prep
Estim.
SP 2
Estim.
Prio

19. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
Backlog
Training Prep
Backlog
Rev
Prep
Estim.
SP 2
Estim. Retro
Prio

20. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
PR
ER
O N
DU
CT OW
Backlog
Training Prep
Backlog
Rev
Prep
Estim.
SP 2
Estim. Retro
Prio

21. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
PR
ER
O N
DU
CT OW
Backlog
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim.
SP 2
Estim. Retro
Prio

22. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
PR
ER
O N
DU
CT OW
Backlog
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim.
SP 2
Estim. Retro
Prio
TEAM

23. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim.
SP 2
Estim. Retro
Prio
TEAM

24. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim.
TEAM
SP 2
Estim. Retro
Prio
TEAM

25. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PO-Roll
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim.
TEAM
SP 2
Estim. Retro
Prio
TEAM
PR
ER
O N
DU
CT OW

26. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim.
TEAM
SP 2
Estim. Retro
Prio
TEAM
PR
ER
O N
DU
CT OW

27. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
SC
R
E
R T
UM
MAS
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim.
TEAM
SP 2
Estim. Retro
Prio
TEAM
PR
ER
O N
DU
CT OW

28. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll TEAM
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
SC
R
E
R T
UM
MAS
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim.
TEAM
SP 2
Estim. Retro
Prio
TEAM
PR
ER
O N
DU
CT OW

29. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll TEAM
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
SC
R
E
R T
UM
MAS
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim. TEAM
TEAM
SP 2
Estim. Retro
Prio
TEAM
PR
ER
O N
DU
CT OW

30. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll TEAM
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
SC
R
E
R T
UM
MAS
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
Estim. TEAM
TEAM
SP 2
Estim. Retro
Prio
TEAM
SC
R
E
R T
UM
MAS
PR
ER
O N
DU
CT OW

31. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll TEAM
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
SC
R
E
R T
UM
MAS
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
PR
ER
Estim. O N
DU
CT OW
TEAM
TEAM
SP 2
Estim. Retro
Prio
TEAM
SC
R
E
R T
UM
MAS
PR
ER
O N
DU
CT OW

32. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll TEAM
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
SC
R
E
R T
UM
MAS
Training Prep
SC
Backlog
R
E
R T
UM
MAS
Rev
Prep
PR
ER
Estim. O N
DU
CT OW
TEAM
TEAM
SP 2
Estim. Retro
Prio
TEAM
SC
R
E
R T
UM
MAS
TEAM
PR
ER
O N
DU
CT OW

33. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll TEAM
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
SC
R
E
R T
UM
MAS
Training Prep
PR
ER
O N
DU
SC
CT OW
Backlog
R
E
R T
UM
MAS
Rev
Prep
PR
ER
Estim. O N
DU
CT OW
TEAM
TEAM
SP 2
Estim. Retro
Prio
TEAM
SC
R
E
R T
UM
MAS
TEAM
PR
ER
O N
DU
CT OW

34. Kick-Starting a Team in Two Weeks
TU WE TH FR MO TU WE TH FR MO TU
MO
PR
ER
O N
DU
CT OW
PO-Roll TEAM
SP 1
PR
ER
O N
DU
CT OW
PR
ER
O N
DU
CT OW
Backlog
SC
R
E
R T
UM
MAS
Training Prep
PR
ER
O N
DU
SC
CT OW
Backlog
R
E
R T
UM
MAS
Rev
Prep
PR
ER
Estim. O N
DU
CT OW
TEAM
TEAM
SP 2
Estim. Retro TEAM
Prio
TEAM
SC
R
E
R T
UM
MAS
TEAM
PR
ER
O N
DU
CT OW

35. #1
company backlog
get one for all!

36. define roles &
#2 responsibilities

37. Sprint # 1 Sprint #
#3
9:00
.......
Sprint Planning 1
Sprint Planning 1
CU
STO MER
Do your Daily Scrum every day! Do your Daily Sc
M
ANAGER
Product Idea
12:00
Review
Sprint
Sprint Planning 2
Sprint Planning 2
VISION
spective
Retro-
PR
ER
Sprint
O N
DU
CT OW
start SC
R
E
R
T
UM
MAS
18:00
TEAM
Day 1
immediately ... 3 days
Product Backlog
Estimation
Estimation
Estimation
Estimation
prioritized
Meeting
Meeting
Meeting
Meeting
PB PB PB
CU CU
M M
STO MER STO MER
ANAGER USER
Releaseplan Releaseplan Update

38. #4 stick to your teams

39. make teams
#5 cross-functional
train them so they
can do the whole
work

40. #6 synchronize teams
Sprint
planning 1
Sprint
planning 2

41. create a
#7
Product Owner Team

42. fix problem no. 1 = ScrumMaster
#8 who does not understands ...
Change Agent
He says “No”
“He fights for the poor”
Far too often, people fear to be a good ScrumMaster.
They do not have the standing!

43. #9 professionalization
‣ software development
‣ product development
‣ finanical numbers

44. #9 professionalization X,
“we do not need to do
we do Scrum.”
‣ software development
“we can‣ do what we want.”
product development
“I am notfinanical numbers
‣ important
anymore - it is the team.”

45. #10 fight the RESISTANCE
CU
STO MER
traditional management
traditional engineering
PR
ER
O N
DU
laciness of thinking CT OW
M
ANAGER
TEAM

46. Lessons Learned
There is no silver bullet!
Significant increase of employees and customers satisfaction
Significant increase of productivity
But:
Joint training of all stakeholders of the organization (incl.
“Geschäftsleitung”) is mandatory!
Scrum is no rocket-science, use your common sense!
Know-How transfer in the cross-functional teams takes
longer than expected (and is still not finished)
Off-site teams need significant additional attention!
Internal Scrum-coach (light-weighted) is very useful
Step-wise approach was the right approach for IS24
Seite 6 | SCRUM at ImmobilienScout GmbH | Boris Gloger / Oliver Zeiler

47. Next Steps
Still no time to relax
No more changes until end of the year, cool down the
organization
Harmonize Scrum and our internal Product-development-
process
Define an IS24-wide prioritized backlog
Rework existing SW/HW architecture to better fit Scrum
Improve management-transparency for larger projects
Proceed with training of internal Scrum-coach
Get the teams some fun after a number of successful sprints
Reconsider interdisciplinary teams, team-size and structure
Seite 7 | SCRUM at ImmobilienScout GmbH | Boris Gloger / Oliver Zeiler

48. 19/20. Mai CSM (deutsch) in Linz,
Austria
27/28. Mai CSM (english) mit
ScrumCooking in München, DE
8/9. Juni CSM (deutsch) mit
ScrumCooking in Wien, Austria
22/23. Juni CSM (english) in Lipno
Lake, CZ