Avg Points
Delivery Throughput
points per ticket
Calculates the average story points per completed task.
💡 Average points tell you the typical complexity of tasks your team handles, like knowing if you usually drive short errands or long highway trips.
What It Measures
Calculates the average story points per completed task.
Why It Matters
Understanding sizing trends and scoping discipline
Monitoring typical task complexity
How It's Calculated
Divides total points by total tickets, treating unsized tasks as 2 points, returning 0 if no tickets.
points ÷ tickets (using size = 2 when missing, returns 0 if no tickets)Concrete Example
If your team completed 60 points across 30 tickets, your average is 2 points per ticket, skewed toward smaller tasks.
What Does a Healthy Score Look Like?
Team-specific, track trends rather than benchmarking against others.
Healthy
2–4 points per ticket (balanced mix)
Watch Out
Under 1.5 or over 6 points per ticket
Needs Attention
Consistent extremes suggest sizing discipline issues
What Moves This Metric?
Goes up when…
More large and complex tasks being completed
Team taking on bigger, riskier initiatives
Tasks being oversized during estimation
Goes down when…
More small bug fixes and quick wins in the mix
Better task decomposition producing smaller units of work
Tasks being undersized or not estimated correctly
Start Tracking Avg Points
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