The Journey of a DevOp

The experiences of one person on what DevOps is and what it takes to transform an organization into a high performing, collaborative one.

Transcript

1. The Journey of a DevOp
2. What is a DevOp?
4. What kind of Journey?
5. Or if you prefer … https://www.youtube.com/watch?v=b4ztfrr8fls
6. Who Am I? • Software Engineer • In my 8th year of experience
7. The ideas contained in this presentation are not unique. ! DevOps is not unique.
8. What is DevOps?
9. A culture of collaboration centered on nurturing business goals quickly while developing a humane work environment.
10. 10 Deploys Per Day Dev & ops cooperation at Flickr ! John Allspaw & Paul Hammond Velocity 2009
11. Why DevOps? http://www.infocaptor.com/dashboard/venture-capital- investment-analytics-on-20-years-of-investment-data
12. Is DevOps About Tools? ! NO
13. But Tools Matter
14. Tools enable automation. Automation means you can work on something more valuable to the company.
15. Experiment. Find the right tool. Use open source to try.
16. Does DevOps mean Dev and Ops become one and the same? ! No.
17. You’ll be a better developer if you know some about operations, and you’ll be better at operations if you know something about development.
18. And Dev and Ops will both be better if they know something about the business.
19. Should developers be on call? ! Maybe.
20. Should you have a DevOps team? ! Maybe.
21. Let’s talk process
22. Process replaces communication, because communication doesn’t scale
23. – Paraphrase of Rands (Michael Lopp) randsinrespose.com Process always starts with a reason. Determine the reason for it and change it if the reason no longer holds.
24. You get the behavior you optimize for.
25. You get the behavior you reward for.
26. So you still want to try this DevOps thing?
27. Management buy-in helps.
28. So how do I get management buy-in?
29. Model the behavior you want
30. Idea from Making Things Happen, by Scott Berkun (Chpt. 16 Power and Politics) Use your sphere of influence.
31. This all takes time, because changing culture takes time.
32. DevOps is hard because it makes everyone vulnerable.
33. Because trust makes you vulnerable, and DevOps is fundamentally about trust.
34. People fear vulnerability. They fear trust. They resist change.
35. - Courtney Nash http://radar.oreilly.com/2015/01/chop-wood-carry-water.html Chop wood, carry water.
36. – John Allspaw, On Being a Senior Engineer http://www.kitchensoap.com/2012/10/25/on-being-a-senior- engineer/ Have generosity of spirit.