I delivered this talk at our internal DevOps Day. In this talk I have examined the principles and practices that enable a successful high-performance devops environment.

1. DEVOPS:
HYPE OR HOPE?
TATHAGAT VARMA
HEAD, STRATEGY & OPERATIONS, WALMART LABS
DOCTORAL CANDIDATE, ISB HYDERABAD

2. HOW
THEY
DO
IT?
HTTPS://YOUTU.BE/OAD_T4WIBM0

3. https://www.dailymail.co.uk/sport/formulaone/article-4401632/Formula-One-pit-stop-does-crew-work.html
• The pit stop crew is usually comprised
of the driver's team mechanics — but
no member will specialise in a certain
role during the pit stop.
• The duties are typically given based on
their physical attributes rather than
their ability to do a specific job, as the
members would be able to handle the
pressure of any role given to them.
• Tyre men tend to be more agile in
order to quickly change the car's
wheels while the jack men are required
to be more physical so they have the
strength to lift the car under intense
pressure.
• The only permanent role is the lollipop
man, which is operated by the chief
mechanic. They stand near the front of
the car (No 15 in our graphic) and
oversee the whole procedure while also
operating the controls; releasing the car
once the pit crew complete the stop.

4. THE “IT’S NOT MY JOB” MANIFESTO…

5. WHAT IS DEVOPS?
https://docs.microsoft.com/en-us/azure/devops/learn/what-is-devops
“DevOps is the union of people,
process, and products to enable
continuous delivery of value to
our end users. The contraction of
“Dev” and “Ops” refers to
replacing siloed Development
and Operations to create
multidisciplinary teams that now
work together with shared and
efficient practices and tools.”

6. https://devopedia.org/devops

7. DEVOPS PRACTICES
Agile and Lean
Planning
Microservices-
based Architecture
Version Control Continuous
Integration (CI)
Continuous Delivery
(CD)
Infrastructure as
Code
Containers Application
Monitoring

8. CULTURAL FOUNDATIONS
From To
Silos (e.g. Dev, QA, Ops, etc.) Cross-functional autonomous teams (i.e. Dev + QA + Ops + …)
Contract between roles Collaboration among role
Local responsibility End-to-End Shared accountability
Handoff-driven processes Agile methodologies
Specs-driven engineering Feedback-driven engineering
Inspection-driven quality Quality built-in
Manual work takes over Automation of routine work

9. HOW WE DO IT?
https://cloud.google.com/devops/state-of-devops/

10. MYTH #1: DEVOPS IS A ROLE!

11. MYTH #2: DEVOPS IS THE ENDS!
https://cloud.google.com/devops/state-of-devops/

12. MYTH #: DEVOPS IS ONE-SIZE-FITS-ALL!
https://editbarry.files.wordpress.com/2011/07/12_xerox_s1.jpeg

13. MYTH #4: TOOLS SOLVE EVERYTHING!
https://devopedia.org/devops

14. MYTH #5: DEVOPS IS PANACEA!
“THROUGH 2022, 75% OF DEVOPS
INITIATIVES WILL FAIL TO FULLY MEET
EXPECTATIONS DUE TO FAILURE TO GROUND
THE INITIATIVE IN BUSINESS VALUE, CULTURAL
CHANGE, AND ESSENTIAL PRACTICES AND
PRINCIPLES.” - GARTNER, 2018
https://www.gartner.com/document/3891969

15. RECAP
• DEVOPS IS A HUMAN PROBLEM – PATRICK DEBOIS,
GODFATHER OF DEVOPS MOVEMENT
• DEVOPS IS A MANAGEMENT PROBLEM – DAMON EDWARDS
• CULTURE, AUTOMATION, MEASUREMENT, SHARING (CAMS)
– DAMON EDWARDS AND JOHN WILLIS, DEVOPSDAYS 2010
• ADDED LEAN (L) TO MAKE IT CALMS – JEZ HUMBLE
• MY TAKE - DEVOPS IS A MINDSET, CULTURE, AND
PHILOSOPHY OF TEAM-BASED PROBLEM-SOLVING
https://itrevolution.com/devops-culture-part-1/