Continuous Delivery: lead time and cycle time

I have seen quite a few people mixing up these terms: lead time and cycle time.

 

I am not sure about the reason for the confusion.  I think Continuous Delivery provides a great example for explaining each one of these important parameters: lead time and cycle time.

 

Manufacturing

Lead time and cycle time are concepts from manufacturing, therefore I use the drawing below for explaining it.  On it, a sample manufacturing assembly line, depicting a visual representation for lead time (L) and cycle time (C).

 

 

  • Lead time: the amount of time a work item takes from the beginning to the end of the workflow
  • Cycle time: the interval of time between two consecutive work items leaving the workflow.
The assembly line provides a visual and physical representation for the workflow. In manufacturing, the workflows as well as the work items are visible. This is not the case on Software delivery. Neither workflow nor work items are naturally visible.  

Continuous Delivery

Continuous Delivery is a software development discipline that fosters faster and more frequently releases. The deliverable is incrementally built on the delivery workflow (represented on the drawing below), starting on coding, and ending on production. Continuous Delivery relies on high levels of build, integration, test, and deployment automation.

Below is a representative drawing for Continuous Delivery.

 
Now I will mix the drawings (Continuous Delivery and assembly line) a little bit. 

 

This drawing creates a visual representation for work items moving on a Continuous Delivery workflow. The box coming out of the assembly line represents a deliverable reaching production. The red X mark with the red arrow represents a work item taken out of the assembly line (failed some test).

 

  • Lead time:  The amount of time a work item takes since it is first committed until it reaches production.
  •  Cycle time: the interval of time between two consecutive deliverable to production.
Continuous Delivery fosters faster and more frequently releases, or using the manufacturing terms: Continuous Delivery fosters shorter release lead time and cycle time.

Paulo Caroli

Paulo Caroli is an author, speaker, and consultant specializing in agile transformations, Lean Inception, and OKRs. With over 30 years of experience—including nearly a decade in Silicon Valley and 18 years at ThoughtWorks—he has helped organizations transition from project to product and from strategy to execution. Creator of the Lean Inception methodology and author of bestselling books like Lean Inception and Team OKR, Paulo is dedicated to empowering teams to align, validate, and deliver real business value.
Assumption Mapping Activity

Assumption Mapping Activity

Assumption mapping is a powerful activity that equips teams to evaluate their assumptions based on their significance and supporting evidence. By following a structured process, teams can clarify their assumptions, enabling well-informed decisions, mitigating risks, and bolstering the likelihood of success in their endeavors.

read more
Design Ahead: Harmonizing Design and Development Timelines for Optimal Results

Design Ahead: Harmonizing Design and Development Timelines for Optimal Results

This article explores the strategic integration of the Design Ahead approach and dual track development methodologies in the realm of software development. By delving into the nuances of design, concurrent workflows, and seamless collaboration, it offers insights into orchestrating a harmonious symphony between design and implementation. From refining user experiences to developing new features, this exploration illuminates the path for organizations seeking to excel in the ever-evolving landscape of software delivery.

read more
Working Backwards – Press Release Template

Working Backwards – Press Release Template

This comprehensive Press Release template provides a structured framework for implementing the innovative Working Backwards approach, a strategy favored by industry leaders like Amazon. By starting with the end customer experience and working backward, this method offers a clear pathway for product development and planning. The template’s sections guide teams in articulating the product/initiative/solution’s significance, key features, and benefits.  Whether for remote collaboration or in-person workshops, this tool equips teams with a collaborative framework to craft impactful press releases.

read more

Pin It on Pinterest