DevOps principles

DevOps joins development and operations around one goal: delivering valuable changes quickly and safely, with fast feedback at every step.

What DevOps is

DevOps is a way of working, not a product or a job title. It removes the wall between the people who build software and the people who run it, so a change travels from idea to production as one shared flow, owned by everyone who touches it.

The CALMS model

CALMS summarizes what a DevOps organization has in place:

  • Culture: shared responsibility for outcomes, without blame when something fails.
  • Automation: repetitive steps run by machines, so people spend time on judgement.
  • Lean: small batches, limited work in progress and less waiting between steps.
  • Measurement: decisions based on data about flow, quality and stability.
  • Sharing: knowledge, tools and lessons travel across teams.

Measuring it: the DORA metrics

Four metrics from the DORA research program show whether delivery is improving. Two measure speed and two measure stability, and high performers improve all four at once:

  • Deployment frequency: how often changes reach production.
  • Lead time for changes: from commit to running in production.
  • Change failure rate: the share of deployments that cause a failure.
  • Time to restore service: how long recovering from a failure takes.

How DevGob applies it

DevGob keeps the work, the change and its evidence on one record, so these metrics are read from real history: every phase transition is timestamped, and a production rollback opens a linked severity-1 bug automatically.

Read it in the documentation

Related topics

DevOps frameworks Scrum, Kanban, ITIL 4 change enablement and CALMS answer different questions. Most teams combine them: one to plan the work, another to govern the change. Continuous delivery Continuous delivery keeps every change ready to release: built, tested and deployable at the push of a button, in small and frequent batches. Change management in DevOps Change management decides which changes need authorization, who gives it and what evidence is kept — without slowing down the changes that don't.

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.

Request a workspace Documentation