Ticket Cycle Time
Task Cycle Times
business days
Measures the average weekday duration from when work starts to when it completes.
💡 Like tracking how long a package takes from warehouse to doorstep, cycle time measures the full journey of a task from start to shipped.
What It Measures
Measures the average weekday duration from when work starts to when it completes.
Why It Matters
Spotting process delays and bottlenecks
Understanding how long tasks take to complete
How It's Calculated
Calculates the average number of weekdays between start and completion for tasks completed in the date range.
AVG(business_days(started_at, completed_at) WHERE completed_at BETWEEN measure_from AND measure_to)Concrete Example
If tasks take an average of 4 business days from start to done, and your sprint is 10 days, each developer can theoretically complete about 2.5 tasks per sprint.
What Does a Healthy Score Look Like?
Lower is better, faster cycle times mean faster delivery and feedback.
Healthy
Under 3 business days
Watch Out
3–7 business days
Needs Attention
Over 7 business days
What Moves This Metric?
Goes up when…
Tasks are too large and should be broken into smaller pieces
Review bottlenecks causing tasks to wait in In Review state
Unclear requirements leading to rework mid-task
Goes down when…
Smaller, well-defined tasks with clear acceptance criteria
Faster code review response reducing wait time
Removing blockers and dependencies before tasks start
Start Tracking Ticket Cycle Time
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