What is DevOps? Definition, benefits and how it works
DevOps explained: what it is, where it came from, its principles and benefits, how it relates to Agile and ITIL, and how to start.
2 min read
Definition
DevOps is a set of practices and a culture that unites software development and IT operations. Its goal is to deliver changes to users quickly, frequently and reliably, with fast feedback on how each change behaves.
Where it came from
The term became popular around 2009, when engineers such as Patrick Debois organized the first DevOpsDays and shared how developers and operators could work as one team. It grew out of Agile, which had sped up development but left releases slow and risky.
Core principles
- Flow: small changes moving continuously from idea to production.
- Feedback: fast signals from tests, monitoring and users.
- Continuous learning: blameless reviews and experiments.
- Automation of repetitive work: builds, tests and deployments.
- Shared responsibility for the result in production.
Benefits
- Shorter time from idea to production.
- Fewer failed changes and faster recovery.
- Less manual, error-prone work.
- Better collaboration between teams.
- Visibility of what is in production and why.
DevOps, Agile and ITIL
Agile organizes how the work is planned and built; DevOps extends that flow to delivery and operation; ITIL describes how IT services and their changes are managed. They are compatible: a modern organization combines agile planning, DevOps delivery and a lightweight, ITIL-inspired control over changes.
How to start
Start with one product and its value stream: map how a change travels from idea to production, find the slowest step and improve it. The guide on how to implement DevOps covers the steps in order.
How DevGob helps
DevGob applies DevOps with governance: the flow of each change is fast, and its approvals and evidence are recorded on the way.
Read it in the documentationFrequently asked questions
Is DevOps a tool?
No. It is a way of working. Tools support it — version control, CI/CD, monitoring — but buying a tool does not make an organization DevOps.
Is DevOps a job role?
Many companies hire “DevOps engineers”, but the idea is a responsibility shared by development and operations, not a separate team in between.
Does DevOps remove controls?
No. Good DevOps automates and records the controls so they stop slowing the flow down.
Keep reading
DevOps with governance, on one record
DevGob plans the work and governs every change on its way to production: backlog, sprints, committee authorizations, install evidence and an audit trail.