liveBook · Manning

Queue depth

As explained in Build High Value Software Systems

The number of work items waiting in a queue for downstream processing.

Queue depth is the number of work items waiting at a stage. A growing queue can signal that demand persistently exceeds that stage’s capacity, making it a clue to where work is delayed. section 6.4 section 6.6

A review queue

A team opens 15 pull requests per week but reviews about 10. Five accumulate each week; improving deployment speed will not resolve the review bottleneck. section 6.4

Use queue depth as one signal in tracing delays:

  • Record how many items wait at each stage, alongside wait time, active work time, and batch size. section 6.6
  • Look for the longest sustained delay, test a small change, then measure whether the queue and lead time shrink. section 6.6
Figure 6.13 A growing bottleneck week by week as reviews become the constraint in the system.

A figure depicts a review queue growing as reviews constrain flow. section 6.4

How Build High Value Software Systems covers it

How deep it goes
Defines queue depth as a bottleneck symptom and a stage-level measure in a practical feature-tracing exercise.
Examples
Shows five weekly pull requests accumulating when review capacity falls short and traces queue depth across a shipped feature.
What you can do after
Diagnose a likely constraint and evaluate an intervention by comparing queue depth, lead time, and activity ratio.
How it connects
Connects queue depth to bottlenecks, value streams, lead time, cycle time, and activity ratio.

Also explained in

Compare how 2 books explain queue depth →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.