Large Tickets
Delivery Throughput
Counts completed tasks sized 6 or more points during the selected period.
💡 Large tickets are the heavy lifts, completing one is a meaningful achievement but too many can create bottlenecks.
What It Measures
Counts completed tasks sized 6 or more points during the selected period.
Why It Matters
Spotting capacity spent on large, riskier work
Tracking completion of major initiatives
How It's Calculated
Counts each completed task with size 6+ points in the date range, treating unsized tasks as 2 points.
COUNT(tasks WHERE done_at BETWEEN measure_from AND measure_to AND COALESCE(size, 2) ≥ 6)Concrete Example
If 3 of your 20 completed tickets were large (6+ points), that is 15% of your throughput on complex initiatives.
What Does a Healthy Score Look Like?
Some large tickets are fine, but too many signal planning or scoping issues.
Healthy
Under 20% of total completions
Watch Out
20–40% of total completions
Needs Attention
Over 40%, most work is too large, risking delivery predictability
What Moves This Metric?
Goes up when…
Complex architectural work or large feature development
Tasks not being broken down during sprint planning
Technical debt paydown requiring sustained effort
Goes down when…
Better story decomposition during planning
Breaking large epics into smaller deliverable milestones
Stronger definition of done encouraging smaller scope
Start Tracking Large 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