In Review Time (Medium)
Task Cycle Times
business days
Measures the average weekday duration medium tasks (3-5 points) spend in "In Review".
💡 A technical report waiting for a manager's sign-off, medium reviews need careful reading but shouldn't take days.
What It Measures
Measures the average weekday duration medium tasks (3-5 points) spend in "In Review".
Why It Matters
Understanding review time for mid-sized work
Benchmarking the review phase for standard features
How It's Calculated
Calculates the mean business days 3-5 point tasks spend in "In Review".
AVG(business_days_in_review WHERE size BETWEEN 3 AND 5 AND completed_at BETWEEN measure_from AND measure_to)Concrete Example
If medium tasks spend 1.2 days in review, that's about one working day of reviewer time per feature, a common target for engineering teams.
What Does a Healthy Score Look Like?
Lower is better, aim for same-day or next-day reviews on medium tasks.
Healthy
Under 1 business day
Watch Out
1–2 business days
Needs Attention
Over 2 business days
What Moves This Metric?
Goes up when…
Reviewer load too high to respond quickly to new reviews
Medium tasks requiring domain expertise that only a few reviewers have
PRs requesting review from unavailable or overloaded teammates
Goes down when…
Team agreements on review response time (e.g., respond within 4 hours)
Pairing reviews with clear documentation or test coverage
Distributed review responsibilities reducing bottlenecks
Start Tracking In Review Time (Medium)
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