Track your team’s productivity by combining metrics from the Productivity Snapshot, Code Review Metric, and Collaboration Snapshot dashboards.
Metrics to Monitor
PRs Merged (Productivity Snapshot)
- Why it matters: Reflects the volume of completed work. A decline might indicate bottlenecks.
- How to use: Monitor for trends and address slowdowns by optimizing the review process.
Days with Commits (Productivity Snapshot)
- Why it matters: Consistent commits indicate steady progress.
- How to use: Identify gaps in activity and ensure team members contribute regularly.
Comments per Review (Code Review)
- Why it matters: Declining comments may indicate reduced engagement in reviews.
- How to use: Encourage meaningful feedback and use it as a sign of a healthy review culture.
PRs Merged without Review (Collaboration Snapshot)
- Why it matters: Unreviewed PRs can lead to quality issues and indicate a rushed process.
- How to use: Enforce review guidelines and ensure all PRs are adequately reviewed.
PRs Opened vs. PRs Merged (Throughput Metrics)
- Why it matters: This metric highlights the balance between initiating work (PRs Opened) and completing (PRs Merged). A consistent or balanced ratio indicates that the team effectively manages new work and completes tasks. Conversely, a growing gap where more PRs are opened than merged may signal inefficiencies, such as review bottlenecks, prioritization issues, or an overload of new work.
- How to use:Monitor trends over time: Compare PRs Opened vs. PRs Merged across different time frames to detect imbalances. Persistent gaps may highlight areas where processes need optimization.Drill down by squad or repository: Use filters to analyze specific teams or codebases to pinpoint where delays occur.Identify causes: Investigate why PRs are not being merged, such as long review times, large PR sizes, or an overburdened reviewer pool.Adjust workflows: Balance workload distribution or set clear priorities to ensure steady progress in merging PRs.
Days with Commits (Productivity Snapshot)
- Why it matters: This metric tracks the number of days the team contributes to the codebase by making commits. It reflects consistency in development efforts and provides insights into overall team engagement. A high number of days with commits suggests steady progress, while sporadic activity could indicate uneven workloads, process inefficiencies, or disengagement.
- How to use:Identify activity patterns: Monitor days with commits across different time frames to ensure the team maintains consistent development momentum.Compare across squads: Use this metric to spot disparities in activity levels between teams, helping to identify overloaded or under-engaged squads.Encourage regular contributions: Promote daily commits to reduce the likelihood of large, complex code changes that can slow down reviews and deployments.
Summary
The Team Productivity guide combines critical metrics like PRs Merged,Issues Resolved,Comments per Review, and Unreviewed PRs to provide a holistic view of your team's efficiency and collaboration. These metrics not only reveal trends in output but also highlight areas for improvement in review practices and task management:
- PRs Merged and Issues Resolved measure the team's ability to complete and deliver work effectively.
- Comments per Review show the depth of engagement and collaboration during code reviews, which is crucial for maintaining quality.
- Unreviewed PRs help identify potential risks stemming from bypassed reviews and declining attention to quality processes.
- Throughput Metrics (PRs Opened vs. PRs Merged) expose imbalances between initiated and completed work, helping identify bottlenecks in the workflow.
- Days with Commits reveal patterns of consistent contributions.
If you notice a high volume of PRs merged but fewer comments per review, it may indicate your team is prioritizing speed over quality. Encourage meaningful reviews by promoting a culture of constructive feedback. Pair this with smaller, more focused PRs to maintain velocity while fostering deeper engagement in reviews.
By balancing these metrics, you can drive both higher output and stronger collaboration, ensuring your team remains productive without compromising code quality or team health.