DevOps

framework · computer science · organizing-schema

Cultural and technical practices unifying development and operations.

DevOps is the cultural and technical movement aimed at dissolving the traditional barrier between software development and IT operations, enabling faster, more reliable software delivery through collaboration, automation, and shared responsibility. The movement was catalyzed by Patrick Debois's 2009 'DevOpsDays' Ghent conference (the term 'DevOps' coined for the event from his neologism), with foundational influences including John Allspaw and Paul Hammond's 2009 Velocity Conference talk '10+ Deploys Per Day: Dev and Ops Cooperation at Flickr', Gene Kim and colleagues' subsequent codification (The Phoenix Project 2013, The DevOps Handbook 2016), and the broader influence of lean manufacturing thinking on software delivery. The framework's core themes — captured in CALMS (Culture, Automation, Lean, Measurement, Sharing) — emphasize cultural alignment between development and operations, automation of build, deployment, infrastructure, and testing, lean flow principles applied to software delivery, measurement of delivery and reliability outcomes, and information sharing across teams. The State of DevOps Report (Forsgren, Humble, Kim) has produced substantial empirical evidence linking DevOps practices to organizational performance through metrics including deployment frequency, lead time for changes, change failure rate, and time to restore service.

Originators

Patrick Debois (term coinage and DevOpsDays movement); John Allspaw and Paul Hammond (foundational Velocity 2009 talk); Gene Kim, Jez Humble, Nicole Forsgren (codification and empirical research) high

Year / Decade

2009 (Allspaw-Hammond Velocity talk; Debois DevOpsDays Ghent); 2013 (Phoenix Project); 2016 (DevOps Handbook) high

Primary sources

Kim, G., Behr, K. & Spafford, G. (2013). The Phoenix Project, Kim, G., Humble, J., Debois, P. & Willis, J. (2016). The DevOps Handbook, Forsgren, N., Humble, J. & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps high

Core components

CALMS: Culture, Automation, Lean, Measurement, Sharing
Cross-functional collaboration between development and operations
Continuous integration and continuous deployment (CI/CD)
Infrastructure as code
Configuration management automation
Monitoring and observability
Blameless post-mortems
Four key DORA metrics (deployment frequency, lead time, change failure rate, MTTR)
Connection to lean manufacturing thinking

Primary use case

Software delivery transformation in organizations of all sizes; foundation for cloud-native development practices; basis for DevOps engineering and platform engineering roles; underpinning of substantial commercial tooling ecosystem (CI/CD platforms, observability, IaC); integration with site reliability engineering and software development culture more broadly.

Common criticisms

'DevOps' has been substantially commercialized into a job title and tool category, often disconnected from the cultural transformation the original movement sought
many 'DevOps engineers' are essentially infrastructure or release engineers without the cross-functional collaboration the framework prescribes
tooling-heavy implementations can substitute for cultural change
the 'you build it, you run it' principle (Werner Vogels) creates real burdens on developers that not all organizations support adequately
DORA metrics, while empirically valuable, can be optimized in ways that don't reflect underlying capability
tension between security teams and DevOps led to DevSecOps as a separate movement
small teams and large enterprises have substantially different DevOps adoption challenges that are sometimes conflated.

Lineage

Parent of: Site Reliability Engineering
Siblings: Site Reliability Engineering, CI/CD, Twelve-Factor App