Improve pull request flow across teams
Pull request flow is how work moves from open PR to merge across your organization. Engineering managers measure it with merge throughput, median lead time, and review responsiveness on the same definitions for every mapped team. DeliveryCompass provides engineering intelligence for GitHub PR delivery — statistics from PR metadata only, not source code.
How do I measure pull request flow across teams?
On a shared date range, compare three signals per team on Team analytics:
| Signal | Healthy pattern | Warning sign |
|---|---|---|
| Merge throughput | Steady or rising merges | Flat volume with growing WIP |
| Lead time | Stable median hours | Spikes week over week |
| Review responsiveness | First review within hours | Multi-day review lag |
What are common PR flow bottlenecks?
- Review lag — PRs sit open while reviewers are overloaded
- Large PRs — hard to review quickly; inflate lead time
- WIP overload — too many open PRs per team (see WIP by team)
- Uneven team load — one team flows; another stalls
Common mistakes when measuring PR flow
- Blaming individuals before checking team-level review lag
- Ignoring bot PRs when volume shifts (toggle Include bots for context)
- Comparing teams with unmapped repositories
- Using commit counts instead of merged work
Staff meeting workflow
Compare teams on the same definitions, note period-over-period deltas on the Overview, and use weekly summary attention callouts to decide where to dig deeper. See staff meeting metrics.
When are spreadsheets enough?
Manual exports work for a single team and occasional reviews. They break when five teams need the same comparison every Monday. See delivery metrics without spreadsheets and choosing delivery metrics.
FAQ
What is a good lead time for a team?
There is no universal target — compare teams on median hours and watch period-over-period trends. See PR lead time by team.
How do I find code review bottlenecks?
Rising review responsiveness while throughput is flat usually means reviewers are overloaded. See code review responsiveness.
Does DeliveryCompass track open PR stages?
Today you get WIP counts and flow KPIs. A PR lifecycle explorer is on the roadmap.
Can I measure AI impact on PR flow?
Toggle bot inclusion for volume context. Dedicated AI impact views are exploring on the roadmap; see AI impact on PR flow.
Pilot scope
DeliveryCompass is Early Access software for GitHub PR delivery metrics. Daily sync, solo workspace, no Jira integration. See pilot scope.