PRs Completed per Week tracks the number of pull requests each developer merges in a given week, serving as a throughput indicator. It provides a rough proxy for individual and team output velocity when viewed alongside PR size and complexity. This metric is most useful in trend analysis rather than absolute comparison, as it must be interpreted in the context of work type and team norms.
PRs merged/closed per developer per week. Elite teams: 15-25 PRs/week with small PRs. Low performers: 2-5 PRs/week. This is THE velocity metric — directly measures how fast developers ship working code.
CRITICALLY AMPLIFIED: Without smart CI tooling (Bazel, Nx, Turborepo), every PR triggers full-repo builds and tests, creating massive bottlenecks. PR throughput can drop 60-80% vs polyrepo without affected-project detection + remote caching. Google's investment in build tools is specifically to maintain PR velocity at scale.
CRITICALLY AMPLIFIED: THE #1 distributed-team productivity killer. Each PR requires cross-TZ review handoffs (12-24h each), merge queue failures during sleep hours, and batching to minimize round-trips. PR completion rate drops 50-70% in distributed teams vs colocated. A colocated dev completing 20 PRs/week may drop to 6-8 PRs/week distributed across 3 TZs.
PR throughput drops 60-80% without smart CI at monorepo scale. Cross-TZ review handoffs add 12-24h per round-trip, crushing velocity.
Completing and shipping work is deeply satisfying. High throughput = visible progress = motivation.
More completed PRs = more deployments. Direct relationship in CD environments.
Higher PR throughput reduces WIP and queue times, cutting lead time.
Developers leave when they feel unproductive. Low PR completion rate signals throttled velocity.
Completing PRs reduces WIP count. Lower WIP = fewer context switches between stalled items.
Each additional hour of review latency directly reduces weekly PR throughput. 24h review → devs batch changes → fewer PRs.
Queue failures reset PR progress. Each failure = hours or days of delay before retry completes.
Slow CI creates iteration bottleneck. 45-min pipeline = max 10-12 iterations/day. Fast 5-min pipeline = 50+ iterations/day.
Each flaky failure requires re-run. At 16% flakiness (Google), most PRs hit at least one flake.
Each context switch costs 23 minutes to recover. High-interrupt environments prevent completing PRs.
Flow state enables 500% productivity bursts. Deep work sessions are when PRs get completed.
Larger PRs take longer to write, review, and merge. 200-line PR = 1 day. 2000-line PR = multiple days.
Test execution is often the CI bottleneck. Long test suites limit iteration speed.
Each PR requires multiple builds (dev build + CI builds + review iterations). 10-min build × 10 iterations = 100 min lost.
High cognitive load slows down all work. Overloaded devs make less progress per hour.
Debt makes every change take longer. 25-50% slower delivery in high-debt codebases.
Good docs eliminate blocking questions. Self-service answers = uninterrupted PR work.
App-switching overhead adds up. 1,200+ toggles/day = 4 hrs/week lost.
Meetings fragment the day. 11 hrs/week in meetings leaves less time for PR completion.
Each PR requires multiple handoffs (submit → review → address feedback → merge). 12-24h per handoff means 2-3 day minimum per PR vs same-day in colocated teams.
Individual productivity boost: +21-98% more PRs per developer. However, organizational impact is UNCHANGED or slightly NEGATIVE due to review bottlenecks and stability risks.
19% slower initially for experienced devs. 4-6 weeks to break even, 8+ weeks for full productivity.