WIP Count
Delivery Throughput
tasks
Shows the average number of tasks in progress simultaneously during the period.
💡 Like having too many browser tabs open, each extra tab slows everything down and increases the chance of mistakes.
What It Measures
Shows the average number of tasks in progress simultaneously during the period.
Why It Matters
Monitoring multitasking levels and context-switching risk
Identifying when you have too many tasks in flight
How It's Calculated
Calculates the average count of tasks in "In Progress" state per day.
AVG(daily_in_progress_count)Concrete Example
If your average WIP count is 4.5 tasks, each developer typically juggles about 4–5 items simultaneously, likely above the optimal limit of 1–2 per person.
What Does a Healthy Score Look Like?
Lower is better, aim for 1–2 tasks per developer at any one time.
Healthy
WIP count ≤ 2× team size
Watch Out
WIP count 2–4× team size
Needs Attention
WIP count over 4× team size, severe context switching
What Moves This Metric?
Goes up when…
Multiple work streams or projects assigned to the same people
Waiting on blockers keeping tasks open longer
No WIP limits in your process
Goes down when…
WIP limits set on your Kanban board
Finishing tasks before starting new ones
Better dependency management reducing blocked time
Start Tracking WIP Count
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com