liveBook · Manning

Cycle time

As explained in Shipping Go: Develop, deliver, discuss, design, and go again

Cycle time is the elapsed time required for an individual process step or stage to complete.

Cycle time is the elapsed time between steps in a delivery pipeline. Because it contributes to overall lead time, shortening slow steps can help deliver customer requests sooner. section 5.4

Speeding up quality checks

A pipeline can run linting, vetting, and testing in parallel to expose problems sooner, although parallel execution costs more computing resources. A hybrid of parallel and sequential steps balances faster feedback with cost. section 5.4

Figure 5.3 Overall lead time is the time from the creation of the task to its delivery to a customer.

Use the lead-time diagram to distinguish the full customer-request-to-delivery interval from the cycle times of its individual pipeline steps. section 5.4

How Shipping Go: Develop, deliver, discuss, design, and go again covers it

How deep it goes
Defines cycle time within lead time and compares parallel, sequential, and hybrid pipeline execution without measuring specific durations.
Examples
Illustrates cycle time with customer-request delivery intervals and parallel linting, vetting, and testing stages.
What you can do after
Apply it via a pipeline by locating slow stages and choosing parallel, sequential, or hybrid execution.
How it connects
Connects cycle time with lead time, pipelines, linting, vetting, and testing.

Also explained in

Compare how 2 books explain cycle time →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Shipping Go: Develop, deliver, discuss, design, and go again. The section links point to the parts of the book it draws on.