The observant noticed that the title of the post is "What is ! DevOps". So what is this !(not) all about?
This is one of my rambling and reflection posts. It's based on observations and random thoughts that are intended to provoke a disccussion, not to be used as a formal definition or guidance.
During a recent workshop I observed a few anti-patterns and scibbled a few notes for this post.
DevOps is !(not):
- A finite journey
- A product
- A rigid framework
- A silver bullet
- Agile on steroids
- All about automation
- An organization where there's no trust, autonomy, or experimentation
- Leadership that drives the WHAT, WHY, and HOW
- Unicorns and magic rainbows
"DevOps is the union of people, process, and products to enable continuous delivery of value to our end users." - http://donovanbrown.com/post/what-is-devops.
It's a prestine definition by Donovan Brown that you'll find stuck on most (all) laptops that ventured anywhere near the ALM | DevOps Rangers or one of Donovan's sessions.
A DevOps mindset fosters
- Growth mindset
- Learning climate
- Reward innovation
- User Empathy
A DevOps mindset enables
More frequent deployments that allows the introduction of new value and fixes quickly.
Change Failure Rate
More successful changes that elliminate rework and allow teams to focus on new value.
Lead Time for Change
Shorter lead times that enable faster feedback and the ability to respond to outages more effectively.
Mean Time to Recovery
Faster time to mitigate failures giving users higher availability.
Any anti-patterns, foster, or enablement points you would add?