DevOps merges software development and IT operations to ship changes faster and more reliably
In short: Software used to be built by one team and run by another, and the handoff between them was slow. DevOps is the practice of integrating development and operations through automation, shared ownership and fast feedback. Its goal is to shorten the time between a code change and that change reaching production without sacrificing quality.
DevOps is best understood as a combination of specific practices, a change in culture and a set of tools. Researchers Len Bass, Ingo Weber and Liming Zhu framed it as a collection of methods aimed at cutting the delay between recording a code change and releasing it into everyday use, while keeping quality high. Its roots go back to proposals in the late 1980s and early 1990s to join software development methods with deployment and operations concepts. The term gained a public identity in 2009, when a conference called DevOps Days was held in Ghent, Belgium, founded by the Belgian IT consultant Patrick Debois.
The approach is usually described by three core ideas: teams sharing responsibility for outcomes, automating the steps of a workflow, and receiving quick feedback. Practices such as continuous integration and continuous delivery are central, because automating builds, tests and deployments is what makes frequent releases manageable. Writer Neal Ford describes a related idea, bringing the pain forward, which means tackling the hardest tasks early so problems surface quickly. Many of these ideas echo older frameworks such as Lean thinking and the Toyota Production System, which emphasised continuous improvement and small batches. DevOps differs from the rigid, top-down approach of ITIL in the 1990s, since it grew bottom-up from the needs of software engineers themselves.
Measurement is a major part of the discussion. DevOps Research and Assessment (DORA) published metrics covering deployment frequency, lead time for changes, change failure rate and failed deployment recovery time. These metrics were criticised by some experts, and the framework has been revised several times, including in 2023, when the stability metric was renamed to reduce confusion, and in 2025, when DORA moved away from ranking teams into performance tiers.
Related specialisations have grown from the same root. DevSecOps builds security checks into each stage of delivery, a pattern described as shifting security left. GitOps keeps deployment configuration under version control so changes can be reviewed and rolled back. DataOps applies similar automation and agile methods to data analytics. Because the term is used in several contexts, people often disagree about what counts as DevOps, so it is best treated as a set of ideas rather than one fixed method.
Opens the Intellect+ feed with this card first. Swipe up for the next one.
Sources
- Summary by Intellect · source: DevOps
To cite this card, link to https://intellectplus.co.uk/app/technology-devops.
How we source, check and correct cards: Editorial standards.
General information, not professional advice. Spotted an error? Flag the card or see corrections and complaints.
Intellect Plus is a visual educational discovery platform for exploring fascinating facts and ideas. Brain Food, Not Brain Rot. What is Intellect Plus?
Related
More in Computing and information technology · More in Technology · Latest · A–Z · All topics