In Progress Time (Large)
Task Cycle Times
business days
Measures the average weekday duration large tasks (8+ points) spend in "In Progress".
💡 Building a complex piece of furniture from scratch, large tasks need sustained, focused effort to complete.
What It Measures
Measures the average weekday duration large tasks (8+ points) spend in "In Progress".
Why It Matters
Understanding if large tasks stall during development
Monitoring development time for complex work
How It's Calculated
Calculates the mean business days 8+ point tasks spend in "In Progress".
AVG(business_days_in_progress WHERE size ≥ 8 AND completed_at BETWEEN measure_from AND measure_to)Concrete Example
If large tasks (6+ points) spend 5 days in active development on average, that's a full work week per major feature, plan your sprints accordingly.
What Does a Healthy Score Look Like?
Lower is better, but some development time is expected for large tasks.
Healthy
3–6 business days
Watch Out
6–10 business days
Needs Attention
Over 10 business days in active development
What Moves This Metric?
Goes up when…
Genuine technical complexity requiring extended research or prototyping
Large tasks not being broken into milestones causing long single-phase runs
Blockers encountered during development adding wait time
Goes down when…
Decomposing large tasks into smaller In Progress milestones
Upfront spikes or research tasks de-risking complex work before development
Regular check-ins catching blockers early
Start Tracking In Progress 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