integrates and automates software development and IT operations to reduce time between change and production while maintaining high quality.

Context: DevOps definition and purpose

In DevOps, is a principle where teams collectively take responsibility for outcomes across development and operations.

Context: DevOps culture and shared ownership

is automating steps in the delivery workflow to reduce manual effort and speed up reliable releases.

Context: DevOps principles: workflow automation

provides timely information about system changes so issues are detected and corrected quickly.

Context: DevOps principles: rapid feedback

Continuous delivery applies the 'bring the pain forward' principle, which causes tough tasks to be tackled early, leading to faster and improved delivery outcomes.

Context: Cause→effect: bring-the-pain-forward to issue detection

automates build, test, integration, and delivery so teams can release changes faster with reduced risk.

Context: CI/CD as a core DevOps enabler

DORA metrics provide measures of delivery efficiency (throughput) and reliability (stability) for continuous improvement. Deployment frequency is defined as the time between deployments.

Context: DORA metric: deployment frequency

DORA includes , which is the percentage of deployments that cause production issues.

Context: DORA metric: change failure rate

In the 2023 State of DevOps update, the stability metric was renamed from 'mean time to recover' to .

Context: DORA metric evolution: failed deployment recovery time

DevSecOps shifts security left by integrating security testing earlier in the lifecycle. This causes security defects to be detected sooner, reducing the risk of vulnerabilities.

Context: Cause→effect: shifting security left to reduced production risk

is static application security testing that checks software without executing it, focusing on security in code.

Context: DevSecOps testing: SAST

is dynamic application security testing that tests software behavior without knowing internal functions.

Context: DevSecOps testing: DAST

DevSecOps uses CWE and OWASP taxonomies for triage and prioritization. Top 25 is a list of frequently occurring software weaknesses maintained by MITRE under CWE.

Context: Security taxonomy: CWE Top 25

GitOps version-controls deployment configuration state, which enables code-review workflows and rollbacks. This causes teams to gain visibility to change, enabling faster tracing and reproduction of .

Context: Cause→effect: GitOps traceability to reproducing issues

DataOps applies Agile and DevOps ideas to data analytics pipelines. It uses statistical process control (SPC) to monitor and verify the pipeline so that trigger automated alerts on anomalies.

Context: Cause→effect: DataOps SPC to automated alerts on anomalies