Prior to DevOps, the “throw it over the wall” model dominated. Once code was deemed complete by Dev, it was handed to Ops for deployment. This link was weak, asynchronous, and document-heavy.
DevOps constructs the Dev-Ops link through three interdependent mechanisms: culture, automation, and measurement. Devops link
DORA (2022). Accelerate State of DevOps Report . Google Cloud Research. Retrieved from dora.dev. Prior to DevOps, the “throw it over the
| Aspect | Development (Dev) | Operations (Ops) | Resulting Conflict | | :--- | :--- | :--- | :--- | | | Rapid feature delivery | System stability & uptime | Misaligned incentives | | Risk Tolerance | High (willing to change) | Low (fear of change) | Deployment friction | | Environment | Local/development | Production | "Works on my machine" syndrome | | Success Metric | New functionality | Mean Time To Recovery (MTTR) | Competing KPIs | Google Cloud Research
Forsgren, N., Humble, J., & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps . IT Revolution Press.
Humble, J., & Farley, D. (2010). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation . Addison-Wesley.