Traditional Internet / e-commerce based companies like Allegro when successful face all challenges of fast and unpredictable growth and are trying to deal with using different tools and methodologies managing it’s IT. The beginning is simple while You are a small IT with just a group of geek fascinated with technologies and results that You achieve. When You start growing Your natural born leaders start to look for methodologies like ITIL that are to help organise IT Operations, make it more efficient, providing fast, reliable and foreseeable services. This somehow goes in pair with waterfall project organised code development organisation which Allegro in fact was. When You are stuck with it, many organisations start, especially in devel areas, get closer to Agile methodologies, and we just jumped in that deep water while IT Operations stood a bit shocked with what happened and after a first shock we had to follow with Agile, with Kanban, and still trying to be IT Operations not being blended in Scrum teams, still being able to provide some data about how and for whom (what products) we actually work.

1. Agile and IT Operations
How to Coexist
and
Not Get Lost
marcin.mazurek@allegro.pl

3. 4

5. { the begining }

6. 40 000 000 of items listed.
15 mln users
1.5 mln new items / day
1 mln transactions / day
11 mln images /day
1999 2013Items Listed

7. SYSOP
NETADM
DEV

8. { when mess becomes too big to stand }

9. {You get the skills, to cope with it... but is it right direction? }

10. Information Technology Infrastructure Library

13. Incydent and Problem Management
Configuration Management
Availability and Capacity Management
Release Management
and many others...

14. { meanwhile in dev world }

15. { SDLC with waterfall }
Project Management Office
Project Support Office

16. { the result }

18. - ITIL became Ops thing
- SDLC - project killer
- PMO / PSO
- silos - dead communication
:(
- hot potato

19. - common language
- KPI awareness (SLA)
- process awareness
- Service Desk
:)
- information flow

20. { ... meanwhile ... }

21. Agile revolution !
grooming
planning
retro
scrum
...

22. { ... meanwhile in Ops... }

23. Network
DBA
SYSADM
ITIL - ops thing
Scrum teams
AGILE - dev thing
Scrum teams
Scrum teams

24. { breaking the silos }

25. Devs
Network
DBA
SYSADM
Scrum team(s)
Devs
Network
DBA
SYSADM
Scrum team(s)
Network
DBA
SYSADM
Shared services
Product #1 Product #n
...

26. Effects:
#1: we need more OPS!
#2: it’s ours not yours problem (no more hot potatos)
#3: maintaining communication among OPS is a challenge.
Devs
Network
DBA
SYSADM
Scrum team(s)
Devs
Network
DBA
SYSADM
Scrum team(s)
Network
DBA
SYSADM
Shared services
Product #1 Product #n
...

27. { Next steps with OPS? }

28. DEVOPS

29. DEVOPS
• let dev guys do it
• give them tools
• teach them how to do it
• start listening to them
• do what is really challanging (SOA)

30. KANBAN
• transparent work backlog
• clear limits in every state and type
• influence of Product Owners onYour work
• rapid feedback loop

31. KANBAN
• transparent work backlog
• clear limits in every state and type
• influence of Product Owners onYour work
• rapid feedback loop
Lessons learnt
separate swimlanes for:
• product - project work
• ops - project work
• maintenance
• incidents - fast lane

32. KANBAN ITIL

33. Where is ITIL?
Devs
Network
DBA
SYSADM
Scrum team(s)
Change Management
Config. Management
.* Management

34. ... so how to coexist and not get lost?

35. ... so how to coexist and not get lost?
• do not forget about OPS,You will need them anyway
• help people in becoming “owners” of products
• appreciate the need for stability (and processes supporting)
• build good cooperation habits
• talk to people, communicate
• adopt and adapt (PDCA)

36. Thank You :)
marcin.mazurek@allegro.pl, http://linkedin.com/in/mmazurek/