devops for executives - agile buddha · what is devops? • devops is the combination of cultural...
TRANSCRIPT
DevOps for Executives- By ShriKant Vashishtha
Myths
DevOps vs Agile
We do Agile
We do DevOps
Someone setting up CI/CD, infrastructure as Code, TDD or any other automation
I am doing DevOps
Let’s include 5 DevOps
Resources
We require a DevOps team to
do this work
A bit of history of DevOps
10+ Deploys Per Day by John Allspaw and Paul Hammond at Velocity 09
DevOpsDays 09, Belgium
What is DevOps?
• DevOps is the combination of cultural philosophies, practices, and tools that increases an organisation’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organisations using traditional software development and infrastructure management processes.
Bodies of Knowledge DevOps Draws Upon
Resilience Engineering or
Human Factors
The Need of DevOps
Working in Different Methodologies
Ops continued to
work old fashioned
Development practices
evolved a lot
– Eli Goldratt on Core Chronic Conflict
When organisational measurements and incentives across different silos prevent the achievement of global,
organisational goals
Core Chronic Conflict Between Dev and Ops
If it’s hard to do something, you are not doing it often enough!If delta is small, so is the risk.
Theory of Constraints
In any flow of work, there is a direction of flow but there is one and only one bottleneck. Any improvement not
made at the bottleneck is an illusion.
In IT Constraint Moves in a Predictable Way
Environment Creation Deployment Testing Architecture Product Owner
Infrastructure As Code - Key to Ops Automation
• Managing your operations environment in the same way you do applications or other code for general release.
• The core best practices of DevOps—like version control, virtualised tests, and continuous monitoring—are applied to the underlying code that governs the creation and management of your infrastructure. In other words, your infrastructure is treated the same way that any other code would be.
• The basic principle is that operators (admins, system engineers, etc.) should not log in to a new machine and configure it from documentation
Managing Bottleneck - Five Focusing Steps
• Identify the constraint
• How to exploit the system’s constraint
• Subordinating everything to above decisions
• Elevate the constraint
• Repeat
Questions?