liveBook · Manning

Lead time

As explained in Microservices Patterns, Second Edition

The elapsed time required for a software change to flow through the deployment pipeline.

Lead time measures how long a software change takes to move from code commit to production. For a deployment pipeline, it is the time from a change entering the queue until the change is deployed. section 1.1.2 section 1.2.1

A pipeline’s lead time has two components:

  • Wait time: how long a change waits in the queue before processing begins. section 1.2.1
  • Processing time: how long the pipeline takes to compile, test, analyze, and deploy the change. section 1.2.1

Setting a pipeline target

A quality attribute scenario can require pipeline tests to complete within 10 minutes after a developer pushes a change, with feedback that the change is releasable. The lead-time target should account for both waiting and test execution. section 5.4.1

Figure 1.6 Fast flow requires a fast deployment that can handle the stream of changes from the development teams
deployment pipeline

The figure illustrates why fast flow depends on a deployment pipeline that can handle the stream of changes from development teams. section 1.2.1

How Microservices Patterns, Second Edition covers it

How deep it goes
Defines lead time and separates it into waiting and processing, without detailing pipeline implementation.
Examples
Uses a 10-minute pipeline-test target and a service pipeline handling smaller, less frequent changes.
What you can do after
Diagnose delivery delays by distinguishing queue wait from pipeline processing time.
How it connects
Connects lead time to DORA metrics, deployment pipelines, fast flow, and testability.

Also explained in

Compare how 10 books explain lead time →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.