liveBook · Manning

Cycle time

As explained in Vibe Engineering

Cycle time is the elapsed time required for work to progress from initiation to completion in a development process.

Cycle time measures the elapsed time from a developer starting a task to its pull request being merged. It exposes delivery speed without treating developer opinion as evidence. AI-assisted coding usually accelerates implementation, but not the thinking, design, or review that surrounds it. section 9.4.2

Interpret cycle-time changes with the surrounding engineering signals:

  • Expect the largest gains on medium-complexity work; simple tasks have little implementation overhead, while complex tasks remain constrained by design and review. section 9.4.2
  • Pair cycle time with pull-request throughput and first-attempt success rate; faster completion can otherwise hide smaller PRs, retry costs, or quality regression. section 9.4.2
  • Treat a sustained increase as a diagnostic signal, not proof of AI-tool failure; investigate configuration drift, project complexity, and team changes. section 9.4.4

A measurable rollout

A team tracking medium-complexity tasks recorded a 25–35% cycle-time reduction after adopting AI coding assistance. The result was smaller for simple and complex work, so the team also monitored PR size, merge throughput, and review success instead of equating speed with feature output. section 9.4.2

Figure 9.7 Visualization of the potential dashboard - state of the art.

A health-check dashboard makes cycle time actionable by pairing the metric with explicit investigation rules, such as reviewing tooling drift after two consecutive monthly increases. section 9.4.4

How Vibe Engineering covers it

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 it assumes
Assumes task, pull-request, merge, and code-review workflows while teaching measurable evaluation instead of perception-based productivity claims.
What you can do after
Diagnose delivery bottlenecks with a health-check dashboard and companion quality metrics rather than relying on developer surveys.
How it connects
Connects cycle time to AI-assisted coding, pull-request throughput, first-attempt success rate, code review, and ROI.

Also explained in

Compare how 5 books explain cycle time →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Vibe Engineering. The section links point to the parts of the book it draws on.