Tickets
Delivery Throughput
Counts the number of tasks that reached Done during the selected period.
đĄ Like counting packages shipped in a day, it tells you how many units of work left the building, regardless of their size.
What It Measures
Counts the number of tasks that reached Done during the selected period.
Why It Matters
Tracking delivered work items
Measuring completion rate over time
How It's Calculated
Counts each task that was marked Done in the date range.
COUNT(tasks WHERE done_at BETWEEN measure_from AND measure_to)Concrete Example
If your team completed 22 tickets this sprint, that is your raw throughput, regardless of size or complexity.
What Does a Healthy Score Look Like?
Compare against your team baseline rather than absolute numbers.
Healthy
Within 15% of your sprint average
Watch Out
30%+ below your moving average
Needs Attention
Declining for 3+ consecutive sprints
What Moves This Metric?
Goes up whenâŠ
Well-groomed backlog with tasks ready to start
Faster review cycles reducing bottlenecks
Good sprint planning producing achievable scope
Goes down whenâŠ
Unplanned work or incidents consuming capacity
Large tasks that spill over sprint boundaries
Review or approval bottlenecks slowing completion
Start Tracking Tickets
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