DevOps and its resulting technical, architectural, and cultural practices represent a convergence of many philosophical and management movement. While many companies have developed these principals independently, they still very isolated (Organisational silos). Therefore, Instead of getting stuck in that rut, let’s look at a few different opportunities to drive DevOps within your business.
The Transformation Process
First, start by defining what’s DevOps… to be honest, there isn’t a single definition for DevOps on the market (yet), but this is a definition that I think it defines DevOps best:
DevOps is a collaboration between development, Operations and Other teams with the recognition that we are tasked with achieving common business goals.
2. DevOps Principles(The goals of DevOps)
Secondly, define some principles for a successful DevOps adoption, I, personally, follow “The Three Ways” by Gene Kim:
The Three Ways
The First Way – System Thinking
- Make work visible
- Reduce our batch sizes and intervals of work
- Build in quality by preventing defects from being passed to downstream work centres
- Constantly optimise for the global goals
- Continuous build, integration, test, and deployment processes
- Creating environments on demand
- Limiting work in process (WIP)
- Building systems and organisations that are safe to change
The Second Way – Feedback Loop
The Third Way – Culture of Experimentation
 Gene Kim. The DevOps Handbook. IT Revolution Press.
 The Phoenix Project, 5th Anniversary Edition
 Jez Humble, David Farley. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation
 DevOps culture
 DevOps dictionary CAMS
 DevOps Agile