DevOps is a new term emerging from the collision of two major related trends. The first was also called “agile system administration” or “agile operations”; it sprang from applying newer Agile and Lean approaches to operations work. The second is a much expanded understanding of the value of collaboration between development and operations staff throughout all stages of the development lifecycle when creating and operating a service, and how important operations has become in our increasingly service-oriented world During this presentation attendees will discover mindset, principles and challenges of DevOps

1. DevOps
A mindset Change
Rami Farran
Agile Tour
Beirut 2015

2. Thank you Sponsors 
GOLD
SILVER BRONZE
HOST

3. Thank you 
Media Partners
Eco-System Partners
Support
Sponsors
Organizer

4. Gartner Says By 2016, DevOps Will Evolve From a
Niche to a Mainstream Strategy Employed by 25
Percent of Global 2000 Organizations

6. Why Now?

7. Not only in IT
• Toyota

9. Software Production
Line

10. DevOps is a cultural and Professional Movement (Adam Jacob)
It's not a tool
It's not a person
It's not dev & ops
CAMS (John Willis)
Culture
Automation
Measurement
Sharing
DevOps Deconstruction/components:
1. Collaboration of People
2. Convergence of Processes
3. Creation and Exploitation of tools

11. • A common perception held by the organization’s members;
a system of shared meaning
• A shared pattern of beliefs, expectations & meanings that
influence and guide the thinking and behaviors of the
members of an organization.
• The culture shapes people who are members in the org
• IBM vs Google
• Culture becomes so much a part of the environment that
participants do not even notice its existence

13. Culture is also a
Liability
• Barrier to change - especially in
established traditional IT
departments
• Barrier to diversity - it puts a
considerable pressure on
employees to conform

14. How to change
cultureOffice
Setup
Process
es
Recogni
tion
Benefits
Quick
Wins Slogans
Dress
Code
Boss
Charact
er
Pictures
Structur
es
Apprais
als
Culture is
an Output.
Not an
Input

15. Changing to DevOps
CultureKaizen
• Evolution
• Low Cost
• Low Risk
• Human Effort
• No Brainer
Innovation
• Revolution
• High Cost
• High Risk
• Technology
• More Thought
DevOps isn’t the goal. It helps you reach your goals.

16. Organization Leaders
• ….Are change champions
• The power of the WHY

17. Patterns and Anti
Patterns
Continuous
Everything Amazon
DR
Google Crazy
Scenarios
Infrastructure as
Versioned Code
Break down the
wall
Willful
Ignorance
EMPATHY
Tribal Knowledge
Be a free man, not
a bottleneck

18. DevOps is a change
of Attitude
• Cultural Change
• Mindset Change
• People Change

19. It takes Organizational
Changes
DevOps Team (Netflix)?
Liaison Team (CE)?
Familiarization.
Paintball (not Dev
vs Ops!!!), Brown
bags, Games
Co-Location
Face to face
Real Time, Real
People
Secondment
Walk a mile in
another man’s
shoes
Event Hosting
Pizza Friday /
Shawerman Friday
Change People
Reassign people
who are unwilling to
change

21. Change Incentives
• Developers are incentivized to
produce and release code
– Ideally error-free code
• Operations are incentivized to
minimize downtime
– Operations knows that the best
protection for production is to accept
no changes
This war ends tonight… Replace
these measurements with shared
responsibility for delivering new
capabilities quickly and safely.

23. That’s all!
• Thank you 