In Progress Time
Task Cycle Times
business days
Measures the average weekday duration tasks spend in the "In Progress" state.
💡 Like the time a chef spends actually cooking. In Progress time is pure development effort, before the dish goes out for tasting.
What It Measures
Measures the average weekday duration tasks spend in the "In Progress" state.
Why It Matters
Identifying how long active development takes
Spotting bottlenecks in the development phase
How It's Calculated
Calculates the mean business days tasks spend in "In Progress" before moving to the next state.
AVG(business_days_in_progress WHERE completed_at BETWEEN measure_from AND measure_to)Concrete Example
If tasks spend an average of 2 business days in In Progress before moving to review, that's your pure development time, useful for estimating coding effort.
What Does a Healthy Score Look Like?
Lower is better, long In Progress times can signal complexity or distraction.
Healthy
Under 2 business days
Watch Out
2–4 business days
Needs Attention
Over 4 business days consistently
What Moves This Metric?
Goes up when…
Tasks are more complex than estimated during planning
Developer context switching between multiple In Progress tasks
Waiting on information or clarification while task stays In Progress
Goes down when…
Smaller, better-defined tasks with clear technical specs
Lower WIP count allowing more focused development
Good upfront design reducing mid-development pivots
Start Tracking In Progress 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