Agile and IT Operations
How to Coexist
and
Not Get Lost
marcin.mazurek@allegro.pl
4
{ the begining }
40 000 000 of items listed.
15 mln users
1.5 mln new items / day
1 mln transactions / day
11 mln images /day
1999 2013Item...
SYSOP
NETADM
DEV
{ when mess becomes too big to stand }
{You get the skills, to cope with it... but is it right direction? }
Information Technology Infrastructure Library
Incydent and Problem Management
Configuration Management
Availability and Capacity Management
Release Management
and many o...
{ meanwhile in dev world }
{ SDLC with waterfall }
Project Management Office
Project Support Office
{ the result }
- ITIL became Ops thing
- SDLC - project killer
- PMO / PSO
- silos - dead communication
:(
- hot potato
- common language
- KPI awareness (SLA)
- process awareness
- Service Desk
:)
- information flow
{ ... meanwhile ... }
Agile revolution !
grooming
planning
retro
scrum
...
{ ... meanwhile in Ops... }
Network
DBA
SYSADM
ITIL - ops thing
Scrum teams
AGILE - dev thing
Scrum teams
Scrum teams
{ breaking the silos }
Devs
Network
DBA
SYSADM
Scrum team(s)
Devs
Network
DBA
SYSADM
Scrum team(s)
Network
DBA
SYSADM
Shared services
Product #1 ...
Effects:
#1: we need more OPS!
#2: it’s ours not yours problem (no more hot potatos)
#3: maintaining communication among O...
{ Next steps with OPS? }
DEVOPS
DEVOPS
• let dev guys do it
• give them tools
• teach them how to do it
• start listening to them
• do what is really chal...
KANBAN
• transparent work backlog
• clear limits in every state and type
• influence of Product Owners onYour work
• rapid ...
KANBAN
• transparent work backlog
• clear limits in every state and type
• influence of Product Owners onYour work
• rapid ...
KANBAN ITIL
Where is ITIL?
Devs
Network
DBA
SYSADM
Scrum team(s)
Change Management
Config. Management
.* Management
... so how to coexist and not get lost?
... so how to coexist and not get lost?
• do not forget about OPS,You will need them anyway
• help people in becoming “own...
Thank You :)
marcin.mazurek@allegro.pl, http://linkedin.com/in/mmazurek/
Agile and IT Operations How to Coexist and Not Get Lost - OSCON 2013
Agile and IT Operations How to Coexist and Not Get Lost - OSCON 2013
Agile and IT Operations How to Coexist and Not Get Lost - OSCON 2013
Agile and IT Operations How to Coexist and Not Get Lost - OSCON 2013
Agile and IT Operations How to Coexist and Not Get Lost - OSCON 2013
Upcoming SlideShare
Loading in …5
×

Agile and IT Operations How to Coexist and Not Get Lost - OSCON 2013

757 views

Published on

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.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
757
On SlideShare
0
From Embeds
0
Number of Embeds
101
Actions
Shares
0
Downloads
13
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Agile and IT Operations How to Coexist and Not Get Lost - OSCON 2013

  1. 1. Agile and IT Operations How to Coexist and Not Get Lost marcin.mazurek@allegro.pl
  2. 2. 4
  3. 3. { the begining }
  4. 4. 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
  5. 5. SYSOP NETADM DEV
  6. 6. { when mess becomes too big to stand }
  7. 7. {You get the skills, to cope with it... but is it right direction? }
  8. 8. Information Technology Infrastructure Library
  9. 9. Incydent and Problem Management Configuration Management Availability and Capacity Management Release Management and many others...
  10. 10. { meanwhile in dev world }
  11. 11. { SDLC with waterfall } Project Management Office Project Support Office
  12. 12. { the result }
  13. 13. - ITIL became Ops thing - SDLC - project killer - PMO / PSO - silos - dead communication :( - hot potato
  14. 14. - common language - KPI awareness (SLA) - process awareness - Service Desk :) - information flow
  15. 15. { ... meanwhile ... }
  16. 16. Agile revolution ! grooming planning retro scrum ...
  17. 17. { ... meanwhile in Ops... }
  18. 18. Network DBA SYSADM ITIL - ops thing Scrum teams AGILE - dev thing Scrum teams Scrum teams
  19. 19. { breaking the silos }
  20. 20. Devs Network DBA SYSADM Scrum team(s) Devs Network DBA SYSADM Scrum team(s) Network DBA SYSADM Shared services Product #1 Product #n ...
  21. 21. 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 ...
  22. 22. { Next steps with OPS? }
  23. 23. DEVOPS
  24. 24. 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)
  25. 25. KANBAN • transparent work backlog • clear limits in every state and type • influence of Product Owners onYour work • rapid feedback loop
  26. 26. 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
  27. 27. KANBAN ITIL
  28. 28. Where is ITIL? Devs Network DBA SYSADM Scrum team(s) Change Management Config. Management .* Management
  29. 29. ... so how to coexist and not get lost?
  30. 30. ... 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)
  31. 31. Thank You :) marcin.mazurek@allegro.pl, http://linkedin.com/in/mmazurek/

×