During last several years DevOps became strong buzzword used almost in every project, team and company. But almost everywhere it is used in very funny and strange context. For example, existing ops guys are renamed to DevOps just to sell them to the client for more money. Or DevOps is used as new job title for some magically powerful person who is able to operate cloud environment and modern infrastructure related tools, leading team of old school ops and participating in management meetings. In this talk I’m going to review all different anti-patterns and bad practices in DevOps landscape using stories from my personal experience as Delivery Manager and independent consultant.

1. Funny stories and anti-
patterns from DevOps
landscape
Mikalai Alimenkou
@xpinjection
http://xpinjection.com

4. Disclaimer
This talk is based on
personal experience

8. Story #1. Dedicated DevOps department

9. Local responsibility syndrome

12. old days problem
nowadays…

13. Story #2. We hired DevOps Engineer

14. Developer + Tester: customer viewReality is not always
so positive

15. Some cases are
even worse…

16. Full engagement is key to success

18. Story #3. Renaming Ops to DevOps

21. • Infrastructure Engineer
• Cloud Infrastructure
Engineer
• Infrastructure Services
Engineer
• Site Reliability Engineer
• Support Engineer
• Release Engineer

23. Story #4. We have DevOps tools in place

26. Story #5. Blame-driven incident
management

29. Story #6. End-to-end developers

31. Story #7. Diversity, diversity everywhere

32. Carl, are you seriously thinking
that the only factor stopping us
from delivery on prod is diversity?
Seriously, Carl?

33. Summary
• Change and grow DevOps culture, not job titles
• Share responsibilities and accountability for success
• Work as a team at all stages of development cycle
• Prefer specialization for complex activities
• Use right tools to maximize automation level
• Establish reliable incident management workflow
• Think about diversity, but not on the first place

34. Success is always in team work

35. What to read?

36. @xpinjection
http://xpinjection.com
mikalai.alimenkou@xpinjection.com