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

999 views

Published on

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

  • Be the first to like this

No Downloads
Views
Total views
999
On SlideShare
0
From Embeds
0
Number of Embeds
94
Actions
Shares
0
Downloads
12
Comments
0
Likes
0
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 Items Listed 1999 2013
  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. Information Technology Infrastructure Library.
  10. 10. The professionals.
  11. 11. Getting into process world... Incydent and Problem Management Configuration Management Availability and Capacity Management Release Management and many others...
  12. 12. { meanwhile in dev world }
  13. 13. { SDLC with waterfall } Project Management Office Project Support Office
  14. 14. { the result }
  15. 15. { remember about people }
  16. 16. - ITIL became Ops thing - SDLC - project killer - PMO / PSO - silos - dead communication :( - hot potato
  17. 17. - common language - KPI awareness (SLA) - process awareness - Service Desk :) - information flow
  18. 18. { ... meanwhile ... }
  19. 19. Agile revolution ! grooming planning retro scrum ...
  20. 20. { ... meanwhile in Ops... }
  21. 21. Network DBA SYSADM ITIL - ops thing Scrum teams AGILE - dev thing Scrum teams Scrum teams
  22. 22. { breaking the silos }
  23. 23. Devs Network DBA SYSADM Scrum team(s) 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) Network DBA SYSADM Shared services Product perspective Product perspective
  24. 24. Devs Network DBA SYSADM Scrum team(s)Next steps with OPS? DEVOPS let dev guys do it give them tools teach them how to do it do what is really challanging (SOA) start listening to them
  25. 25. 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
  26. 26. KANBAN ITIL
  27. 27. Where is ITIL? Devs Network DBA SYSADM Scrum team(s) Change Management Config. Management .* Management
  28. 28. ... so how to coexist and not get lost? - do not forget about OPS,You will need them anyway - build good cooperation habbits - talk to people, communicate - adopt and adapt (PDCA) - help people in becoming “owner” of product - appreciate the need for stability (and processes supporting)
  29. 29. Thank You :) marcin.mazurek@allegro.pl, http://linkedin.com/in/mmazurek/

×