DevOps is a combination of cultural philosophies, practices, and tools that aim to increase an organization's ability to deliver applications and services at high velocity. It emphasizes automation, communication, and collaboration between development and operations teams. The DevOps movement originated in the late 2000s due to the need for more innovation in systems and bridging the gap between developers and IT teams. Key figures like Patrick Debois and Andrew Shafer helped popularize the concept of having development and operations work more closely together through conferences like DevOpsDays, starting in 2009.

1. What is DevOps?
Everything you need to know
1

2. iDevOp.org
The word “DevOps” is concatenation of two short
abbreviations.
"Dev“ for Development
and
"Ops" for Operations
Dev + Ops
2

3. iDevOp.org
From lots of definitions over the internet,
here are three easy ones.
Definitions
1
By iDevOp.org2
1 By Amazon aws
By Jez Humble
3

4. iDevOp.org
DevOps is a cross-disciplinary community of practice
dedicated to the study of the building, evolving and
operating rapidly-changing resilient systems at scale.
By Jez Humble
1
4

5. iDevOp.org
It is a set of practices that emphasizes automation,
communication, and collaboration among developers and
operations professionals, in order to build, test and deploy
application faster and more reliably.
DevOps culture is built on the collaboration of development and
IT teams which traditionally functioned as two separate
departments. Possibly unknown to each other.
By DevOp.org
12
5

6. iDevOp.org
DevOps is the combination of cultural philosophies, practices,
and tools that increase an organization’s ability to deliver
applications and services at high velocity: evolving and
improving products at a faster pace than organizations using
traditional software development and infrastructure
management processes.
By Amazon aws
3
6

7. iDevOp.org
In Simple Words both the developers and the
operations professional working together on an
application or service.
7

8. iDevOp.org
Here engineers work throughout all stages of a software
life-cycle.
This includes developing, testing and deploying it.
Their skills and responsibilities are not limited to a single
stage.
8

9. iDevOp.org
History
9

10. iDevOp.org
Even DevOps may not know the story of this movement.
If yes,
not the journey from a single audience to the present
praise.
Why history?
10

11. iDevOp.org
If you are familiar with it, you can skip it.
11

12. iDevOp.org
or if you are a bit lazy to read, here is a video by Damon
Edwards on
The Short History of DevOps.
12

13. iDevOp.org
Inventions follow Need
13

14. iDevOp.org
It is the result of the increasing need for
innovation in systems side of technology
between
2007 and 2009.
14

15. iDevOp.org
The DevOps movement inherits from the Agile
System Administration movement and the
Enterprises system management (ESM) movement.
15

16. iDevOp.org
No one came forward to bridge the gap between
developers and the IT teams.
In The Beginning,
16

17. iDevOp.org
Except for a few people like Patrick Debois,
Gene Kim, and John Willis
17

18. iDevOp.org
Let me introduce you to two most
important people of this journey
Patrick Debois
and
Andrew Shafer
18

19. iDevOp.org
A software development consultant.
In his 15+ years experience, he had worked as a
developer, network specialist, system administrator,
tester, and project manager.
Patrick Debois
19

20. iDevOp.org
Patrick Debois (left) -- aka the Godfather of DevOps -- with John Willis.
20

21. iDevOp.org
He wanted to learn every inch of IT. So, he took
projects in different areas of IT to better
understand them.
21

22. iDevOp.org
Andrew Shafer - Software Developer
22

23. iDevOp.org
The start,
23

24. iDevOp.org
Patrick was handling a large data-center
migration for the Belgium government.
24

25. iDevOp.org
He was the system administrator and also in-charge of testing.
25

26. iDevOp.org
To fulfill his job he had to work with both Development
and Operations teams.
26

27. iDevOp.org
He noticed a large gap between their work practices.
27

28. iDevOp.org
It was the first time when Patrick started thinking on
ways to minimize the boundary between
development and IT teams
28

29. iDevOp.org
Software developer Andrew Shafer presented "Agile
Infrastructure" also known as "birds of a feather"
concept at the Agile 2008 conference in Toronto.
2008
29

30. iDevOp.org
He failed to gain an audience, surprisingly no one
except Patrick Debois.
30

31. iDevOp.org
Patrick was his only audience at that session.
31

32. iDevOp.org
You can have a laugh on the fact that Andrew Shafer
himself skipped his own session.
It's Ok. I can understand
32

33. iDevOp.org
Patrick was only one who was interested in this idea
at that time.
You can Guess
33

34. iDevOp.org
John Allspaw, senior vice president of technical
operations at Flickr, and Paul Hammond director of
engineering at Flickr presented "10+ deploys per day:
Dev and Ops Cooperation at Flickr" at the O'Reilly
Velocity 09 Conference in San Jose.
2009
34

35. iDevOp.org
This was the first practical implementation of the concept
35

36. iDevOp.org
The results were promising,
10+ was huge at that time
36

37. iDevOp.org
Patrick Debois after watching the presentation
decided to start his own conference.
37

38. iDevOp.org
He popularized the concept through a series of
"devopsdays" conferences starting in 2009 in
Ghent, Belgium.
38

39. iDevOp.org
The new Name
39

40. iDevOp.org
Patrick Debois in InfoQ interview told that
“I picked ‘DevOpsDays’ as Dev and Ops working
together because ‘Agile System Administration’ was too
long,” he said.
“Therenever was a grand plan for DevOps as a word.”
April 2012
40

41. iDevOp.org
More Coming Soon
41

42. iDevOp.org
Thank
you
42

43. iDevOp.org43