In this talk I share about "DevOps" and "Culture Shock"; People believe "DevOps" is about automation, but what you have missed it is "C.A.L.M.S"

1. Culture ShockBMK Lakshminarayanan

2. If culture isn’t the first part of explaining DevOps,
you’ve missed the point
-John Willis
Responsibility of DevOps is to enable the Business; DevOps is culture change, you cannot directly change
culture but the behaviours; change in behaviour becomes culture.

3. • Production outage is always operations team issue
• Logging Issue vs Fixing Issues
• What is the charge code?
• My resource is key resource and is always busy
• I will do when time permits
• I do not trust
• It is always their fault
• Why I need to change?
• I know how to do my work
• My work important than yours
• Threat, if I automate I might not get $$$

4. What is wrong with my culture?
A culture is defined as the organisation’s pattern of
response to the problems and opportunities it encounters.
- Ron Westrum

5. High-Performance
When you put great people together they do great
things.
- Jody Mulkey

6. High-Performance
Considering your ability to have a greater impact on an
organisation beyond your own job title

7. High-Performance
Understanding that your job is more than a job, and
that you work more than a mere checklist

8. Attitude for Learning
Ego is force field
of learning

9. Generalizing Specialist
Robert A. Heinlein said it best: "A human being should be able to change a diaper,
plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet,
balance accounts, build a wall, set a bone, comfort the dying, take orders, give
orders, cooperate, act alone, solve equations, analyze a new problem, pitch
manure, program a computer, cook a tasty meal, fight efficiently, die gallantly.
Specialization is for insects."
- See more at:
http://www.agilemodeling.com/essays/generalizingSpecialists.htm#sthash.gQtNyFwO.dpuf

10. Culture Change
Starts with you