“DevOps” is short for “Development and Operations,” but there is nothing concise about this term. DevOps has become so loaded, complex, and contentious that I can’t discuss the return on investment (ROI) without defining it first.
Think about DevOps this way: there are martial arts, there is jujutsu, and there is judo, an offshoot of jujutsu that you saw in the Rio Olympics. Software development is martial arts, Agile is jujutsu, and DevOps is judo.
Six traits distinguish DevOps and produce the ROI we seek to measure:
1. Continuous Integration (CI): A process in which developers and testers validate new code.
2. Continuous Delivery (CD): The process of creating releasable artifacts.
3. Dynamic Cloud infrastructure: The virtualization of infrastructure that optimizes computing resources.
4. Test Automation: The scripts that carry out both functional and interface testing.
5. Security Automation: The scripts that perform security checks, increasingly known as DevSecOps
6. Monitoring: Constant measurement of the environment to proactively address issues
Development, operations, and quality assurance (QA) work collaboratively to make DevOps possible. They do DevOps not because it’s hip and mystifying, but rather to meet business objectives. Let’s be frank: companies spend a boatload on development expecting to make a ship-ton of money.