Queue time is elapsed time when a work item is waiting rather than being actively worked. In a delivery flow, waiting adds elapsed time without adding value; it can occur in a backlog or while a pull request awaits review. section 6.4 section 9.5
One practical measure defines wait time as lead time minus cycle time: the time between a request being created and work starting. For example, with a 15-day lead time and 3-day cycle time, the item waited 12 days before anyone touched it. section 9.5
Look for persistent queues, not just long processing stages. If a team opens 15 pull requests a week but can review only 10, five accumulate each week. Faster coding or deployment will not resolve that constraint and may add more work to the queue. section 6.4
Table 9.4 Exercise worksheet. Fill in one row per completed work item
|
Work item
|
Lead Time
|
Cycle Time
|
Wait time
|
Activity time
|
Activity ratio
|
|
Fix login timeout
|
|
|
|
|
|
|
Add export button
|
|
|
|
|
|
|
Update payment validation
|
|
|
|
|
|
|
Implement new API
|
|
|
|
|
|
|
Version bump a dependency
|
|
|
|
|
|
Use the worksheet to record wait time alongside lead time, cycle time, and activity ratio for each work item. section 9.5

