Work-in-progress (WIP) inventory is work that has started but has not moved through the next step. In API delivery, it can be partially completed design or delivery work awaiting further processing. At a specific handoff, count ready work items waiting in the queue: developer-ready API review tickets awaiting review are one example. section 2.11 section 2.4
A queue can grow when work is batched. If reviews happen only twice a week, ready tickets wait for the next review session. Record the queue size and the review cadence when investigating a delay; a count alone does not show why work is waiting. Large WIP batches consume resources and capital. section 2.4 section 2.11
An API review backlog
Count the developer-ready tickets awaiting review, then distinguish them from tickets that still need corrections, information, or resolved dependencies. The latter are not ready for the reviewer. Track that readiness separately with percent complete and accurate (%CA), and use a chart to make the queue and delay visible in an A3 problem report. section 2.4


