Find a term
Get clear definitions of software delivery metrics and the practices behind them, from deployment frequency to recovering from a failed change.
Search results
174 termsAbstraction branching
Abstraction branching is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsAftercare monitoring
Aftercare monitoring is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsAlert to action time
Alert to action time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsArtifact advancement
Artifact advancement is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsArtifact promotion
Artifact promotion is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsArtifact version
Artifact version is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsAutomated deployment
Automated deployment is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBackward-compatible change
Backward-compatible change is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsBlue-green deployment
Blue-green deployment is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBranch lifetime
Branch lifetime is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBuild artifact
Build artifact is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBuild failure rate
Build failure rate is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBuild provenance
Build provenance is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsBuild queue time
Build queue time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsBuild reproducibility
Build reproducibility is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsCanary deployment
Canary deployment is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsCanary rollout
Canary rollout is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsChange approval
Change approval is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsChange approval time
Change approval time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsChange failure
A change failure is a production change that causes an incident, service degradation, rollback, hotfix, or another defined operational problem. The organization must define which outcomes count before calculating a rate.
DORA and DevOpsChange failure analysis
Change failure analysis is the structured examination of a software change that caused a production failure or required immediate intervention. It connects the change, failure mode, user impact, detection, response, and prevention work so the delivery system can learn.
DORA and DevOpsChange failure definition
Change failure definition is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsChange failure rate
Change failure rate is the proportion of production deployments that require immediate corrective intervention, such as a rollback or urgent fix. It relates failures to deployed changes instead of counting every incident affecting a service.
DORA and DevOpsChange failure rate definition
Change failure rate definition is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsChange lead time
Change lead time is the elapsed time between a code change being committed to version control and that change being deployed in production. It describes a specific portion of software delivery, rather than the full time from an idea to a customer outcome.
DORA and DevOpsChange lead time definition
Change lead time definition is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsChange retry rate
Change retry rate is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsChange size
Change size is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsChange traceability
Change traceability is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsChange validation time
Change validation time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsCI feedback time
CI feedback time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsCode to production time
Code to production time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsCommit to deploy time
Commit to deploy time is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsConfiguration as code
Configuration as code is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsConfiguration state drift
Configuration state drift is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsConnection draining
Connection draining is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsConsumer-driven contract
Consumer-driven contract is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsContinuous delivery
Continuous delivery is a software development approach in which changes are kept in a releasable state through automated build, test, and delivery practices. A production release may still require a human decision.
DORA and DevOpsContinuous deployment
Continuous deployment is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsContinuous integration
Continuous integration is the practice of merging small code changes into a shared branch frequently and validating them with automated builds and tests. Its value comes from early feedback, not from running a pipeline on a schedule alone.
DORA and DevOpsContinuous integration practice
Continuous integration practice is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsContinuous quality testing
Continuous quality testing is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOpsContinuous testing practice
Continuous testing practice is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsContract-first development
Contract-first development is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsCorrective release
Corrective release is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsDark launch
Dark launch is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsData migration
Data migration is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsDatabase backfill
Database backfill is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsDeclarative infrastructure
Declarative infrastructure is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsDelivery pipeline
Delivery pipeline is a software delivery concept used to describe a specific event, interval, control, or operating condition in the path from source change to production behavior. A useful definition names the boundary, unit, and decision the measure supports.
DORA and DevOps