Introduction to the concept of DevOps, how to use it and some statistics

1. Introduction to DevOps
F. Garavaglia
Vers. 1.0 / November 2017

2. I am Francesco Garavaglia
o over 10 years of experience in IT consulting companies.
o Took part in large scale projects (Energy Markets, Bank, Insurance)
o Pay attention to Software architecture and Business value
o Photographer
o High-Aggressive-I-eat-you-German-Shepherd-Protected-by
You can find me at Francesco.garavaglia@gmail.com
Hello!

3. Agenda
◉What is DevOps?
◉Once upon a time
◉Why DevOps?
◉How to start DevOps?
◉DevOps, Finally
◉DevOps Stats
◉Q/A

4. What is DevOps?

6. “
“It’s a movement of people who think its time for
change in the IT industry – time to stop wasting money,
time to start delivering great software and building
systems that scale and last”
Patrick Debois

7. DevOps Philosophy

10. a true story
Once Upon a Time

11. Once Upon a time, in 2013

14. Once Upon a time

15. Why DevOps?

16. Why
Lead Time
DEV OPS
Feedback
Wall of
Confusion
Shorten

17. Why

18. Why does it matter?

19. Why does it matter?

20. How to start DevOps?

21. DevOps Principles

22. DevOps Practices

25. Continuous Integration

26. CI is about what people do
Not about what Tools they use

27. CI is a practice
◉ Discipline to
integrate frequently
◉ Strive to make
small Changes
◉ Strive to fast
feedback

28. Continuous Delivery

30. DevOps, Finally

31. DevOps Culture

32. DevOps Goals
Cultural Change – Collaboration,
Cooperation, Transformation to a
learning Organization (Improved
knowledge retention & deeper
Knowledge understanding of the
business
Increased responsiveness to
business needs (increased
understanding to prioritize for feature
requests from the business ability to
communicate)
Improved quality of the code
(reduction of defects in each
environment deployment & increase
test coverage of the code
More Agile developments (increased
development capabilities for product
feature)
People Tecnology
Process
More agile change process (increased
rate of acceptance for new features &
visibility across the product lifecycle
Improved Quality of Sofware deploy
(reduction of incidents per deploy)
More frequent releases
(increase of velocity of product
releases)
Improved Visibility into IT process
& requirement

34. Add DevOps into Dev
Enhance Service
Design with
Operation al
Knowledge
◉ Reliability
◉ Performance
◉ Security
◉ Test Them
◉ Build Feedback
Loops from
Production
◉ Monitoring and
KPI Dashboards
Culture of
Responsibility:
Whether your code
passes test, gets
deployed and stays
up for users as your
responsibility
Make Development Better with Ops
– Productionlike enviromnents
– Power tooling

35. Accelerate Flow to Production
Reduce batch size
Automated
environments means
identical dev / test /
prod
Create safety through automation
◉ Continuous Integration/Testing
◉ Automated Regression Testing
◉ Continuous Delivery
◉ Continuous Deployment
◉ Feature Flags (A/B Testing)
◉ Security Testing

36. Add Dev into Ops
Don’t do tasks for
people
◉ Build tools so they
can do their own
work
Monitoring/logging /
metrics feeds back
into dev (and the
business)
Developers Do
production
support/empower
◉ ops acceptance

37. DevOps stats

38. DevOps Stats
https://www.slideshare.net/PuppetLabs/2016-state-of-devops-report-webinar

39. DevOps Stats

40. DevOps Stats

41. DevOps Stats

42. DevOps Stats

43. DevOps Topology

44. Any questions ?
You can find me at
◉ Francesco.garavaglia@gmail.com
Thanks!

45. Credits
https://www.linux.com/blog/what-devops-patrick-
debois-explains
https://www.slideshare.net/PuppetLabs/2016-
state-of-devops-report-webinar