Delivery pipeline

How cycle time is measured

Same model as LinearB cycle time: work started → work delivered to production.

Cycle time

First commit → production release

Time from when work started (first commit) until the change is live in production. Sum of coding, pickup, review, and deploy when all phases are known.

Coding time

First commit → PR opened

Time spent building the change before the pull request is opened. Draft time before open counts as coding.

Pickup time

PR opened → first review

Wait time until a teammate starts review. If the PR merges with no review, this spans open → merge. By default, weekend hours are excluded (Mon–Fri).

Review time

First review → merge

Time from the first human review activity until the pull request is merged. By default, weekend hours are excluded (Mon–Fri).

Deploy time

Merge → production release

Time from merge until the earliest successful deployment to a configured production environment. Uses 24/7 elapsed time (deploy windows and overnight waits count).

Rework time

Not a separate cycle phase

LinearB folds rework into review time (first review → merge). Use Time to approve / Time to merge on Delivery for approval sub-phases; we do not split requested-changes loops yet.

Totals on this page are the sum of coding + pickup + review + deploy per merged PR. Deploy time uses 24/7 hours; other phases exclude weekends (Mon–Fri) by default. Change timezone or mode in Settings → Metric accuracy. Bot reviews are excluded from pickup and review.