In Progress Time (Medium)
Task Cycle Times
business days
Measures the average weekday duration medium tasks (3-5 points) spend in "In Progress".
💡 The focused cooking time for a multi-course meal, medium features take a couple of days to build properly.
What It Measures
Measures the average weekday duration medium tasks (3-5 points) spend in "In Progress".
Why It Matters
Understanding typical development time for mid-sized work
Benchmarking development phase for standard features
How It's Calculated
Calculates the mean business days 3-5 point tasks spend in "In Progress".
AVG(business_days_in_progress WHERE size BETWEEN 3 AND 5 AND completed_at BETWEEN measure_from AND measure_to)Concrete Example
If medium tasks spend 2.2 days in development on average, that's 2–3 days of focused coding per feature, a reasonable benchmark.
What Does a Healthy Score Look Like?
Lower is better, medium tasks should complete development in 2–3 days.
Healthy
1.5–3 business days
Watch Out
3–5 business days
Needs Attention
Over 5 business days
What Moves This Metric?
Goes up when…
Tasks requiring more technical design work than originally planned
Integration challenges or third-party dependencies slowing progress
Frequent context switching disrupting deep work
Goes down when…
Clear technical design and architecture decisions before coding starts
Protected focus time for complex development work
Pair programming to accelerate difficult sections
Start Tracking In Progress 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