Cycle Time (Medium)
Task Cycle Times
business days
Shows the average cycle time for medium tasks sized 3-5 points.
💡 Standard shipping versus express, medium tasks are your reliable baseline for feature delivery.
What It Measures
Shows the average cycle time for medium tasks sized 3-5 points.
Why It Matters
Benchmarking mid-sized delivery speed
Understanding typical feature completion time
How It's Calculated
Calculates the average weekdays between start and completion for 3-5 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) BETWEEN 3 AND 5)Concrete Example
If your 3–5 point tasks average 3.5 business days, that's your typical feature delivery time, plan sprints knowing most features take about 3–4 days.
What Does a Healthy Score Look Like?
Lower is better, medium tasks should complete within a sprint.
Healthy
2–4 business days
Watch Out
4–7 business days
Needs Attention
Over 7 business days, medium tasks are consistently stalling
What Moves This Metric?
Goes up when…
Scope creep expanding tasks beyond their original estimate
Multiple review cycles required before tasks can be closed
Cross-team dependencies causing wait time
Goes down when…
Tighter scoping and clearer acceptance criteria during planning
Pair programming or early feedback reducing rework
Streamlined review processes for standard feature work
Start Tracking Cycle Time (Medium)
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