PR lead time by team (GitHub)
PR lead time is the elapsed time from when a pull request is opened until it is merged. Engineering managers use team-level median lead time to spot flow problems before staff meetings. DeliveryCompass computes lead time from GitHub merge timestamps for mapped repositories — statistics only, no source code storage.
What does lead time measure?
DeliveryCompass uses median hours from PR creation to merge for PRs merged in the selected period. Outliers affect the median less than the average. Full formula: lead time definition.
How does team scope differ from org scope?
Org lead time includes all ingested repos. Team lead time includes only repos mapped on Teams & repos. Unassigned repos count at org level only.
How do I use lead time in reviews?
Compare teams on the same date range on Team analytics. Pair rising lead time with review responsiveness to distinguish review lag from large-PR problems. See PR flow.
FAQ
What is a good lead time target?
No universal hours target — watch period-over-period trends and team comparisons instead of absolute numbers.
Does lead time include time before the PR is opened?
No. It measures open → merge only. Issue-to-PR cycle time is not in the pilot.
How do bots affect lead time?
Bot-authored PRs are excluded by default. Toggle Include bots when you need automation in the mix.
Pilot scope
Daily GitHub sync, not real-time. See pilot scope.