Velocity metrics
The top velocity metrics are:- Median wait-to-first-review: median time for merged PRs from ready for review to first human review. Falls back to PR creation when ready-for-review events are unavailable.
- Average review cycles until merge: how many revision rounds PRs go through.
- Average PR cycle time: total creation-to-merge time.
- Average time in review: first review to final approval.
- Average time from approval to merge: post-approval operational delay.
A decreasing trend is positive — it means PRs are getting reviewed faster. The trend indicator
reflects this: a downward change appears in green.
Throughput metrics
- PRs merged per developer: average merged output for active authors.
- PRs reviewed per developer: average review load for active reviewers.
Code volume
Track lines added and lines deleted as activity context, not as a quality score.Lines of code are a measure of activity, not productivity. A large refactor that deletes more
lines than it adds can be more valuable than a feature with thousands of new lines. Use code
volume as context alongside the other metrics, not as a standalone indicator.
Team members table
The team members table includes per-developer delivery and review metrics:
Click column headers to sort. Use the search field to filter by GitHub username.
CSV export
Click the download button above the table to export the current view as a CSV file. The export respects your active filters and time period selection. The filename includes the export date for easy tracking. Use this export for lightweight reporting or trend tracking outside cubic.Tips for interpreting delivery metrics
- Compare trends, not absolutes.
- Read metrics together to find bottlenecks.
- Large PRs naturally increase cycle times and review rounds.