Velocity & Visibility
Tracks delivery speed, review efficiency, and team activity patterns.
Velocity Metrics
Cycle Time
Time from first commit to PR merge.
| Status | Threshold |
|---|---|
| Good | <3 days |
| Warning | 3–7 days |
| Critical | >7 days |
Components: development time (first commit → PR creation) + review time (PR creation → first review) + revision time (first review → merge).
Review Time
Time from PR creation to first review.
| Status | Threshold |
|---|---|
| Good | <24 hours |
| Warning | 24–48 hours |
| Critical | >48 hours |
Rework Rate
Percentage of commits made after the first review.
Formula: (commits after first review / total commits) × 100
| Range | Meaning |
|---|---|
| <20% | Good initial quality |
| 20–30% | Normal iteration |
| >30% | Unclear requirements or weak review feedback |
Bottleneck Detection
- Stuck PRs: PRs waiting for review >48 hours
- Overloaded Reviewers: Reviewers with too many PRs in queue
Visibility Metrics
- Cross-Repository Activity: Work distribution across multiple repositories
- Active PR Tracking: Open PRs by repository, contributor, and age
- Review Participation: Who reviews, how often, and whether workload is fair
- Activity Heatmaps: Activity by day of week, contributor, or repository
Charts
- Velocity Trends: Cycle time and review time over time
- Flow Efficiency Waterfall: Time spent in each PR stage
- Bottleneck Heatmap: Overloaded reviewers and high-load time periods
Action Items
High cycle time: reduce PR size, streamline review process.
High review time: set review SLAs, use review rotation.
High rework rate: clarify requirements before coding, improve review feedback quality.