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 termsHotfix rate
Hotfix 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 DevOpsIdea to production time
Idea 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 DevOpsImmutable artifact
Immutable artifact is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsImmutable infrastructure
Immutable infrastructure 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 DevOpsIncident budget
Incident budget 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 DevOpsIncident-triggered deployment
Incident-triggered 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 DevOpsInfrastructure as code
Infrastructure as code 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 DevOpsMain branch health
Main branch health 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 DevOpsMean time to mitigate
Mean time to mitigate 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 DevOpsMean time to resolve
Mean time to resolve 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 DevOpsMean time to restore
Mean time to restore is the average elapsed time needed to restore a service after an incident or failure. The result depends on which events count, how recovery is defined, and whether the distribution is summarized by a mean or another statistic.
DORA and DevOpsMerge to deploy time
Merge 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 DevOpsOperational readiness
Operational readiness 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 DevOpsPipeline as code
Pipeline as code 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 DevOpsPipeline failure rate
Pipeline 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 DevOpsPipeline flakiness
Pipeline flakiness 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 DevOpsPolicy validation as code
Policy validation as code is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsPost-deployment monitoring
Post-deployment monitoring 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 DevOpsPreview environment
Preview environment is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsProduction change volume
Production change volume 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 DevOpsProduction readiness
Production readiness 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 DevOpsProduction release event
Production release event is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsProgressive delivery
Progressive delivery 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 DevOpsPull request to production time
Pull request 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 DevOpsQuality gate
Quality gate is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsReconciliation loop
Reconciliation loop is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRecovery point objective
Recovery point objective 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 DevOpsRecovery time objective
Recovery time objective 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 DevOpsRecreate deployment
Recreate deployment is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease approval
Release approval is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease automation
Release automation is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease batch size
Release batch 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 DevOpsRelease cadence
Release cadence 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 DevOpsRelease candidate
Release candidate 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 DevOpsRelease change correlation
Release change correlation is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease engineering
Release engineering is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease freeze
Release freeze is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease frequency
Release frequency 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 DevOpsRelease health check
Release health check is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease observability
Release observability 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 DevOpsRelease orchestration
Release orchestration is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease readiness
Release readiness 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 DevOpsRelease readiness review
Release readiness review is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease readiness signal
A release readiness signal is evidence used to decide whether a software change or release is sufficiently understood, tested, and supported for its intended production boundary. It may combine quality checks, risk, review, deployment, observability, and operational information.
DORA and DevOpsRelease reversal
Release reversal is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease rhythm
Release rhythm is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRelease train
Release train 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 DevOpsRelease window
Release window is a release engineering and DevOps concept for controlling how software changes are prepared, introduced, or understood.
DORA and DevOpsRoll-forward
Roll-forward 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 DevOpsRollback
Rollback 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