DevOps
DevOps is a way of working that joins software development (Dev) and IT operations (Ops) into one flow. Teams share ownership of building, releasing and running a service, and they rely on automation and fast feedback instead of hand-offs between separate groups. It is a culture first and a toolchain second.
How it works
Take a team that used to release once a quarter through a ticket to operations. In a DevOps model the same team writes the code, owns the CI/CD pipeline and carries the pager. Infrastructure is described in code, so a new environment is a pull request, not a two-week request. The team then tracks the four DORA measures: deployment frequency, lead time for changes, change failure rate and time to restore service.
Why it matters in production
Hand-offs hide cost. When the people who write the code also run it, they feel the failures and fix causes, not symptoms. The common failure is renaming an ops team "DevOps" and changing nothing else. Tools without shared ownership only move the queue.
See also
On the One2N blog
Further reading
