In Progress Time (Small)
Task Cycle Times
business days
Measures the average weekday duration small tasks (1-2 points) spend in "In Progress".
💡 The quick preparation time for a simple recipe, small tasks should move through development almost instantly.
What It Measures
Measures the average weekday duration small tasks (1-2 points) spend in "In Progress".
Why It Matters
Verifying that small tasks flow quickly through development
Benchmarking development speed for quick-win items
How It's Calculated
Calculates the mean business days 1-2 point tasks spend in "In Progress".
AVG(business_days_in_progress WHERE size ≤ 2 AND completed_at BETWEEN measure_from AND measure_to)Concrete Example
If small tasks (1–2 points) spend 0.8 days in development on average, that's less than a day of coding per task, exactly what you'd expect.
What Does a Healthy Score Look Like?
Lower is better, small tasks in development should take under a day.
Healthy
Under 1 business day
Watch Out
1–2 business days
Needs Attention
Over 2 business days, small tasks are taking too long to develop
What Moves This Metric?
Goes up when…
Small tasks turning out to be harder than estimated
Context switching pulling developers away mid-task
Undiscovered dependencies making quick tasks complex
Goes down when…
Good task scoping ensuring truly small tasks stay small
Dedicated focus time reducing interruptions
Resolving dependencies before starting small tasks
Start Tracking In Progress Time (Small)
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