Cycle Time (Large)
Task Cycle Times
business days
Shows the average cycle time for large tasks sized 6 or more points.
💡 A major construction project, large tasks take longer by nature, but tracking their cycle time shows whether they're stalling or progressing.
What It Measures
Shows the average cycle time for large tasks sized 6 or more points.
Why It Matters
Assessing whether big initiatives stall in your process
Monitoring completion time for complex work
How It's Calculated
Calculates the average weekdays between start and completion for 6+ point tasks, treating unsized tasks as 2 points.
AVG(business_days(started_at, completed_at) WHERE completed_at BETWEEN measure_from AND measure_to AND COALESCE(size, 2) ≥ 6)Concrete Example
If your 6+ point tasks average 8 business days, that's almost two full working weeks per large task, a signal to consider breaking them down further.
What Does a Healthy Score Look Like?
Lower is better, if large tasks consistently span multiple sprints, break them down.
Healthy
5–8 business days
Watch Out
8–15 business days
Needs Attention
Over 15 business days, tasks are too large or getting blocked
What Moves This Metric?
Goes up when…
Tasks are genuinely complex and require extended research or development
Unclear requirements discovered mid-task causing scope expansion
Review cycles on large PRs taking significantly longer
Goes down when…
Better decomposition of large work into smaller milestones
Splitting large PRs into smaller, reviewable chunks
Earlier alignment on requirements reducing mid-task pivots
Start Tracking Cycle Time (Large)
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