Cycle Time (Small)
Task Cycle Times
business days
Shows the average cycle time for small tasks sized 1-2 points.
💡 A quick errand versus a cross-town trip, small tasks should be your fastest lane.
What It Measures
Shows the average cycle time for small tasks sized 1-2 points.
Why It Matters
Verifying that small work flows quickly through your process
Benchmarking efficiency on quick-win items
How It's Calculated
Calculates the average weekdays between start and completion for 1-2 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) ≤ 2)Concrete Example
If your 1–2 point tasks average 1.5 business days to complete, your small task pipeline is healthy, these should move fastest.
What Does a Healthy Score Look Like?
Lower is better, small tasks should complete in 1–2 days.
Healthy
Under 2 business days
Watch Out
2–4 business days
Needs Attention
Over 4 business days, small tasks are getting stuck
What Moves This Metric?
Goes up when…
Tasks sized as small but actually requiring more work than estimated
Review delays even for minor changes
Dependencies blocking progress on what should be quick wins
Goes down when…
Better task definition ensuring small tasks are truly small
Priority review for small, low-risk changes
Reducing dependencies before picking up small tasks
Start Tracking Cycle 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