Cycle time
Cycle time is the elapsed time required for a work item, process, or production cycle to move from a defined start point to completion.
Build High Value Software Systems
The elapsed time required for work to move through a production or delivery process.
- How it is used
- Measures elapsed execution-phase delivery time so teams can locate delays after work begins.
- How deep it goes
- Defines start and finish boundaries, distinguishes adjacent measures, and gives a timestamp-based measurement procedure.
- Examples
- Uses a 20-day lead time with five days of cycle time and an exercise tracing recent completed changes.
- What you can do after
- Diagnose/debug delivery flow by measuring completed changes, finding the longest delay, and checking the effect of one intervention.
Read how Build High Value Software Systems explains cycle time →
Optimization Algorithms: AI techniques for design, planning, and control problems
Cycle time is the time allocated for a workstation to complete its assigned tasks and pass the product onward.
- How it is used
- Frames assembly-line capacity and task-assignment decisions by limiting each workstation’s available completion time.
- How deep it goes
- Defines the measure, embeds it in SALBP objectives, and demonstrates parameter use without deriving the optimization internals.
- Examples
- Uses cycle-time settings of 4 and 48.0 in Python runs that report workstation counts and workloads.
- What you can do after
- Configure it in an assembly-line balancing model and evaluate resulting station counts and workloads.
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.
- How it is used
- Uses cycle time to identify pipeline steps whose optimization can reduce customer-facing lead time.
- 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.
Read how Shipping Go: Develop, deliver, discuss, design, and go again explains cycle time →
Developer Experience on Kubernetes
The elapsed time required for a delivery cycle or for a change to receive the relevant feedback.
- How it is used
- Measures how quickly development workflows deliver changes or return quality feedback.
- How deep it goes
- Explains inner and outer loops, identifies delay sources, and gives five-minute and sixty-minute stage targets.
- Examples
- Uses pre-integration reviews, feature branches, automated tests, build artifacts, and staged acceptance checks as delay and feedback examples.
- What you can do after
- Evaluate delivery workflows by locating review, integration, testing, and acceptance delays that extend feedback or production delivery.
Read how Developer Experience on Kubernetes explains cycle time →
Vibe Engineering
Cycle time is the elapsed time required for work to progress from initiation to completion in a development process.
- How it is used
- Measures delivery speed from task start to merged pull request when evaluating AI-assisted coding outcomes.
- How deep it goes
- Defines the interval, reports task-complexity effects, and supplies monitoring rules, but does not specify implementation internals.
- Examples
- Uses medium-complexity task reductions, smaller pull requests, and a health-check threshold for consecutive monthly increases.
- What you can do after
- Diagnose delivery bottlenecks with a health-check dashboard and companion quality metrics rather than relying on developer surveys.
What to know first
- code reviewCode review is the systematic examination of source code or proposed changes to assess correctness, quality, risks, or conformance to requirements or standards.
- continuous integrationContinuous integration is a software development practice of frequently integrating changes into a shared codebase and automatically validating them with builds, tests, or other checks.
- deployment pipelineA deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- continuous improvementContinuous improvement is a recurring process in which outcomes or feedback guide successive changes intended to improve a system, process, or result.
Related concepts
- lead timecontrasts with · Lead time is the elapsed time from when work is initiated or becomes available until its result is completed, delivered, or made available to its recipient.
- control chartmeasured by · A control chart is a statistical process-monitoring graph that plots process measurements over time against a center line and control limits to assess variation.
- deployment pipelinemeasured by · A deployment pipeline is a repeatable sequence of stages that builds, tests or validates, packages, and delivers software changes toward release or deployment.
- activity ratiomeasured by · An activity ratio is the proportion of total lead time spent on active work rather than waiting or other non-progressing periods.
- batch sizeuses · Batch size is the number of items grouped for processing together in a single batch or computational operation.
Questions about cycle time
What is cycle time?
Cycle time is the elapsed time required for a work item, process, or production cycle to move from a defined start point to completion.
Which Manning books explain cycle time?
Build High Value Software Systems, Optimization Algorithms: AI techniques for design, planning, and control problems, Shipping Go: Develop, deliver, discuss, design, and go again, Developer Experience on Kubernetes and Vibe Engineering.
What should I know before learning cycle time?
Manning books that teach cycle time usually introduce code review, continuous integration, deployment pipeline and continuous improvement first.
What is the difference between cycle time and lead time?
Cycle time is the elapsed time required for a work item, process, or production cycle to move from a defined start point to completion. Lead time is the elapsed time from when work is initiated or becomes available until its result is completed, delivered, or made available to its recipient.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.




