This document provides an introduction to DevOps. It defines DevOps as a cultural and professional movement focused on building and operating high-velocity organizations. The document discusses the history of DevOps, noting that while concepts like Agile infrastructure have existed since 2009, the term "DevOps" is relatively new. It also provides two definitions of DevOps, including seeing it as the co-evolution of practices with the underlying activity. The rest of the document covers various aspects of DevOps including culture, automation, lean practices, measurement, and sharing through examples from companies that have implemented DevOps.

1. introduction to devops
2016-08-17
Gérard de Vos
@gr4rd
gjdevos@gmail.com

2. Agenda
● /me
● One definition of devops
● Old or new? A bit of history
● Another definition of devops
● Where?
● CALMS
● Takeaways

3. /me
Now:
Previously:
Also:

4. One definition of devops
“Devops is a cultural and professional movement, focused on how we build and
operate high velocity organizations, born from the experiences of its practitioners.”
- Adam Jacob,
CTO & founder of Chef
http://readwrite.com/2015/07/29/devops-people-not-technology/

5. It is not new

7. It is new
In 2009 things came together:
● Agile infrastructure thread by Patrick Debois et al.
● "10+ Deploys Per Day: Dev and Ops Cooperation at Flickr" by John Allspaw
and Paul Hammond https://www.youtube.com/watch?v=LdOe18KhtT4
● Lessons Learned blog, and later “Lean Startup” book, by Eric Ries
● “Continuous Delivery” by Jez Humble and David Farley
And something called "cloud".
http://itrevolution.com/the-convergence-of-devops/

8. http://www.devopsdays.org/events/2009-ghent/

9. A bit on evolution
Credit: shutterstock.com

10. http://blog.gardeviance.org/2014/05/it-all-gone-bit-wardley-here.html

11. Another definition of devops
“Devops is co-evolution of practice with the evolution of an underlying
activity.”
- Simon Wardley
Researcher @ Leading Edge Forum
Previously: VP Cloud at Canonical, CEO at Fotango
http://blog.gardeviance.org/2015/04/devops-weve-been-here-before-we-will-be.html

12. https://twitter.com/swardley/status/717167176386482176
http://blog.gardeviance.org/2015/04/devops-weve-been-here-before
-we-will-be.html

13. http://blog.gardeviance.org/2015/10/agile-vs-lean-vs-six-sigma.html

14. http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/

15. http://www.jedi.be/blog/2012/05/12/codifying-devops-area-practices/

17. CALMS
● Culture
● Automation
● Lean
● Measurement
● Sharing
http://itrevolution.com/devops-culture-part-1/
(https://www.chef.io/blog/2010/07/16/what-devops-means-to-me/)

18. Culture

20. https://twitter.com/sethwalker/status/523161292920872960

21. http://blog.gardeviance.org/2015/04/devops-weve-been-here-before
-we-will-be.html

22. Design for failure
“The best way to avoid failure is to fail constantly.”
http://techblog.netflix.com/2010/12/5-lessons-weve-learned-using-aws.html

23. “Waking up developers at 3am is a great feedback loop: defects get fixed very
quickly”
MobBrowser case study
http://www.slideshare.net/realgenekim/devops-kanban-meet-up-32212

24. “You built it, you run it”
- Werner Vogels
CTO Amazon
https://queue.acm.org/detail.cfm?id=1142065

26. http://www.slideshare.net/adriancockcroft/when-developers-operate-and-operators-develop

27. https://dl.dropboxusercontent.com/u/1018963/Articles/SpotifyScaling.pdf
http://nomad8.com/wp-content/uploads/2014/02/Squads-Chapters-Guilds-in-one-page.graffle.pdf

28. Blameless (or blame-aware) post-mortems
“Take a hard look at how the accident actually happened, treat the engineers
involved with respect, and learn from the event.”
https://codeascraft.com/2012/05/22/blameless-postmortems/

29. Automation
Continuous integration
Continuous delivery
Infrastructure as code
-------------------------------+
Reduce risk
Increase speed
Usually in that order

32. Automation
Git / VCS
Automated testing. Test driven development etc.
Deployment tooling
ChatOps
These document and share the decision making process and development
progress.

33. Lean
W. Edwards Deming, Henry Ford, Taiichi Ohno et al.
Toyota Production System
Kaizen. Continuous Improvement
Muda. Remove ‘waste’

34. https://en.wikipedia.org/wiki/Value_stream_mapping

35. https://goatcan.do/2014/04/04/get-your-head-out-of-your-aas/

36. Measurement
The feedback loop
How you know what you are doing

37. “only about 1/3 of ideas improve the metrics they were designed to improve.”
Online Experimentation at Microsoft: http://ai.stanford.edu/~ronnyk/ExPThinkWeek2009Public.pdf

39. “The ability to learn faster than your competitors may be the only sustainable
competitive advantage.”
- Arie de Geus
Former head of Shell's Strategic Planning Group

40. Sharing
Share discoveries and lessons.
Work in the open:
repositories, wikis,
trackers, monitors.

41. http://www.slideshare.net/KrisBuytaert/velocity2013-mh

42. GDS
https://www.gov.uk/government/organisations/government-digital-service/about
https://github.com/alphagov

43. USDS

44. More

45. More
Devops Meetup Amsterdam (duh)
http://www.meetup.com/DevOpsAmsterdam/
Devopsdays
http://www.devopsdays.org/
Devopsdays Amsterdam will be back June 28-30 2017 :-)
Devopsweekly.org newletter
http://www.devopsweekly.com/

46. In short
● Devops is about people.
● Devops is, also, just part of evolution.
● It is not for everywhere. Most powerful in the middle.
● It is not just for those with job labels of “dev” or “ops”.
● It is still young and evolving. (you have to) Adapt it to your organization,
department, team.
● Keep learning and improving.
● Share and enjoy!

47. Questions?

48. Thank you!