Throughput (and work in progress)
Throughput is how much work your system of delivery completes in a period; pairing it with work-in-progress (WIP) explains flow more than counting tasks alone.
These pages explain common engineering and delivery metrics in plain language. Definitions vary by company, toolchain, and industry; we highlight typical usage and caveats. Nothing here is legal, financial, or professional advice, and it is not a substitute for judgment in your own context.
Metrics can be misused for surveillance or stack ranking. We do not recommend using them that way. DORA performance bands from research are contextual—not targets for individuals or hiring decisions.
See the Engineering metrics glossary hub for all terms.
Definition
Throughput is the rate at which work items are completed—for example, stories, PRs merged, or releases per week. It describes system output, not how busy individuals appear.
Work in progress (WIP) is how many items are actively being worked at once. In Kanban-style thinking, high WIP often lowers throughput and increases cycle time because of context switching, queueing, and blocked work.
How teams typically measure it
- Count completed items per interval that match your planning grain (avoid mixing epics and subtasks).
- Track average WIP on a board or in review queues to see load relative to throughput.
- Seasonality (holidays, hiring freezes) makes short windows noisy; use trends, not single weeks, for decisions.
Common pitfalls
- Using throughput as a quota without quality signals—teams may rush “done” work that creates downstream defects.
- Ignoring type of work: maintenance and incidents compete with feature throughput; splitting views avoids false narratives.
Related terms
Browse other entries in the glossary.