Transforming IT Culture: An Introduction to DevOps

Slides for the talk I gave at the 2016 University of Wisconsin - Madison Information & Technology Leadership Conference. Without the talk (which was not recorded), the slides are less helpful, save for the last slide with resources.

Transcript

1. Transforming IT Culture: An Introduction to DevOps Joshua Zimmerman @TheJewberwocky
2. • What is DevOps? • Trends in the community • What a DevOps culture could mean for UW • Where do we go next? • Questions/discussion
3. Definitions are a doozie.
5. A simple definition lacking context: DevOps is development and operations working together.
7. 2001: The Agile Manifesto We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
8. It doesn’t matter how quickly you can deploy software if you can’t get it into production.
10. 2008: Agile Infrastructure & DevOps
11. “Well, that escalated quickly.” - Ron Burgundy (Anchorman)
12. What is DevOps?
13. What does DevOps mean to other organizations?
14. C.A.M.S.
15. Culture https://www.flickr.com/photos/nathanreading/6003060174/
16. Automation https://commons.wikimedia.org/wiki/File:Rube_Goldberg%27s_%22Self-Operating_Napkin%22_(cropped).gif
17. Measurement https://commons.wikimedia.org/wiki/File:Measuring_the_diameter_of_the_water_bead_2.JPG
18. Sharing https://commons.wikimedia.org/wiki/File:Children_sharing_a_milkshake.jpg
19. Just culture means that we build empathy into the way we respond to incidents.
20. A key goal of a DevOps culture is to develop empathy, so we can’t talk about it without talking about diversity.
21. DevOps can be defined as a culture in which the needs of the organization are considered holistically, where all units work together to actively enable other units, and where units work to continuously improve themselves for the good of their colleagues and the organization.
22. So, what about UW?
23. We have a proportionally large number of IT units for an organization our size.
24. That’s a lot of silos.
25. “Organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations” (Conway’s Law)
26. Many of our projects are “too big to fail.”
27. Most of the IT staff on campus doesn’t have purely traditional IT roles.
28. Why should we care about DevOps?
29. How do we move forward?
30. Reassess how we communicate.
31. Put a new emphasis on sharing.
32. Start having open discussions about IT culture on our campus.
33. Questions or comments?
34. Resources Mentioned in talk: • Agile Infrastructure and Operations - http://www.jedi.be/presentations/IEEE-Agile-Infrastructure.pdf • DevOps Cafe - http://devopscafe.org/ • How do Committees Invent? - http://www.melconway.com/Home/Committees_Paper.html Other great DevOps resources: • DevOps Weekly - http://www.devopsweekly.com/ • Arrested DevOps - https://www.arresteddevops.com/ • The Ship Show - http://theshipshow.com/ • The Phoenix Project - https://search.library.wisc.edu/catalog/9912162690202121 • Effective DevOps - http://shop.oreilly.com/product/0636920039846.do • SRE Weekly (sometimes has DevOps topics) - https://sreweekly.com/