Github Metrics

Github metrics play a vital role in evaluating the efficiency and productivity of software development teams. In this knowledge base article, we will discuss the importance of these metrics and guide you through setting them up to ensure that your team stays on track with its goals.

Key Github Metrics

1. Throughput: Throughput measures the number of pull requests a team completes during a specific period. This metric helps teams assess how often they open pull requests to ensure developers commit and get peer-reviewed often.
2. 85% Cycle Time: Cycle time is the duration between the start and completion of a pull request. The 85% cycle time metric indicates the time within which 85% of pull requests are completed. This metric helps teams understand how long it takes to submit work for review and how quickly it merges.
3. Status Breakdown: This metric provides a detailed analysis of how long pull requests spend in each status, such as "Pickup" "Approval" and "Merged" Understanding the time spent in each status can help teams identify areas where they can streamline their pull request workflow.
4. Code Activity: This metric highlights code activity over the last week, ensuring that coding is happening against the current work items. By monitoring this metric, teams can track their progress and promptly address any potential issues or blockers.
5. Pull Request Reviewer Distribution: This metric helps teams understand if everyone is pulling their weight in reviewing pull requests. A balanced distribution of review responsibilities ensures that the team maintains high-quality code and a streamlined review process.
6. Past Performance: Analyzing a team's performance over the last quarter provides valuable insights into trends and areas for improvement. This metric helps teams set realistic goals and make data-driven decisions for future planning.

Setting Up Github Metrics

To set up Github metrics for your team, follow these steps:

1. Create an account or login into your ScatterSpoke account.

2. Navigate to the organization-level integrations.

3. Follow the instructions for the Github Metrics inside the modal that will walk you through connecting your Github repositories to your ScatterSpoke organization.

4. Once you connect Github & ScatterSpoke, it's time to select which repositories you want to link to your ScatterSpoke team.

5. It will take 5-10 minutes to process your team's data, depending on the size of the Github project. ScatterSpoke pulls the last quarter of Github repositories and feeds it into our insights engine.

6. After your data is done processing, you will be able to see all the metrics & insights we collected about your Github repositories.

‍

Continuous Improvement

Github metrics provide valuable insights into your team's performance and workflow, allowing you to make data-driven decisions for continuous improvement. By setting up these metrics and monitoring them regularly, you can ensure your team stays on track

After getting all your metrics and insights about your Github repositories, we recommend reviewing them with your team a few times a week and discussing them at your next retrospective.  This will help your team focus on what's stopping them from delivering more value during your retrospective and devise action plans to fix them.

‍