change lead time
The time from a commit being made to that commit running in production.
In more detail
It is computed per deployment by subtracting the commit timestamp from the deploy timestamp. The median is the honest summary, because one long-forgotten branch would drag an average anywhere.
Example
change lead time 4.0 hours (median)Related terms
- DORA metrics — Five measures of software delivery from the DORA research: change lead time, deployment frequency, failed deployment recovery time, change fail rate and deployment rework rate.
- deployment log — A file the deploy job appends one line to per deployment, holding the time, the commit and the result.
- median — The middle value when all observations are sorted: half are faster and half are slower.
- lead time — The clock time from when a piece of work starts to when it is finished, including all the time it spent waiting.
- deployment frequency — The number of deployments to production over a period, or equivalently the time between deployments.
- commit — A saved snapshot of the whole project in Git, together with its author, committer, time, message and a pointer to the commit before it.
Taught in
- DORA Metrics: Measuring Your Pipeline — Continuous Integration & Continuous Delivery Pipelines
- Feature Flags and DORA Metrics — Continuous Integration & Continuous Delivery Pipelines
- What DevOps Actually Is — DevOps & Site Reliability Engineering
- Throughput: Change Lead Time And Deployment Frequency — DevOps & Site Reliability Engineering
- The Four Keys History And Retiring MTTR — DevOps & Site Reliability Engineering
- The Pitfalls Of Measurement — DevOps & Site Reliability Engineering