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.
Kim, G., Behr, K., & Spafford, G. (2013). The Phoenix Project: A Novel about IT, DevOps, and Helping Your Business Win . IT Revolution Press.
DORA (2022). Accelerate State of DevOps Report . Google Cloud Research. Retrieved from dora.dev. Devops link
Humble, J., & Farley, D. (2010). Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation . Addison-Wesley.
This disconnect created a negative feedback loop: Ops resisted frequent deployments, leading Dev to bypass formal processes, leading to brittle deployments, leading Ops to increase resistance further. Prior to DevOps, the “throw it over the
The link between Development and Operations is the core innovation of DevOps. It is not a simple pipeline but a multi-faceted connection comprising cultural empathy, automated workflows, and unified measurement. Organizations that successfully implement this link transition from a fragile, handoff-based model to a resilient, high-trust system where rapid innovation and stable operations are complementary, not contradictory. As software continues to eat the world, the strength of the Dev-Ops link will remain a primary differentiator between high- and low-performing technology organizations.
The primary link is psychological. DevOps replaces the traditional separation of concerns with a shared accountability model. The principle of “You build it, you run it” (inspired by Werner Vogels at Amazon) forces developers to consider operability from the first line of code. Simultaneously, operations engineers gain visibility into the development pipeline. This cultural link reduces blame and encourages problem-solving over finger-pointing. Kim, G
Forsgren, N., Humble, J., & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps . IT Revolution Press.