In Review Time (Large)
Task Cycle Times
business days
Measures the average weekday duration large tasks (8+ points) spend in "In Review".
💡 A legal contract review, large changes require careful scrutiny and naturally take longer, but the goal is to keep it manageable.
What It Measures
Measures the average weekday duration large tasks (8+ points) spend in "In Review".
Why It Matters
Identifying if large tasks stall during review
Monitoring review time for complex work
How It's Calculated
Calculates the mean business days 8+ point tasks spend in "In Review".
AVG(business_days_in_review WHERE size ≥ 8 AND completed_at BETWEEN measure_from AND measure_to)Concrete Example
If large tasks spend 2.5 days in review on average, that's nearly half a work week just for review, a strong signal to split large PRs.
What Does a Healthy Score Look Like?
Lower is better, long review times on large tasks often signal the PR is too big.
Healthy
Under 1.5 business days
Watch Out
1.5–3 business days
Needs Attention
Over 3 business days. PRs are too large to review efficiently
What Moves This Metric?
Goes up when…
Large PRs combining many changes making review cognitively expensive
Reviewer hesitation due to insufficient context or documentation
Critical path reviewers being unavailable
Goes down when…
Breaking large features into smaller, reviewable PR series
Adding thorough PR descriptions, screenshots, and test coverage notes
Scheduling review walk-throughs for complex architectural changes
Start Tracking In Review 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