Overall Performance Score indicates your overall status in terms of performance. Even in the first look at this metric, you will have a general idea of your development cycle and how you have been performing compared to the previous month.
The grades are calculated by analyzing your teams' behaviors in various aspects such as their patterns in coding, reviewing, testing and deployment phases, their individual and team-based efficiency, risky commits they push, whether they are following the best practices, their daily activities and many others.
Additionally, the overall details of projects, repositories and developers that have been included in the score calculation are also demonstrated.
Projects With Action
The number of projects containing repositories that have been contributed to in the selected period. The considered projects will contain active repositories. The projects that do not contain any active repositories are excluded from the active project scope. The other reports in the corresponding section are based on active projects.
Repositories With Action
Active Repositories are defined as whether they have actions such as commits, PRs (open, merge, reviews, comments), and releases. When any of these actions are taken for the repository, it will be considered an active repository in the corresponding iteration.
Team Members With Action
Team Members are defined as participants who take actions in terms of pushing commits, opening PRs, conducting reviews, commenting on PRs. In other words, contributing to the projects through actions in evaluated repositories.
Project Resource Overview
This report is showing a detailed analysis of the resource usage in the company. This valuable key metric provides crucial data on the areas where the focus of the team members is driven based on the projects defined.
The resource analysis is made based on the impact on top of the time spent for the actions of commit, pull request, comment, merge. These efforts are collected by taking contributors and projects into consideration.
If the issue repository with work log data is integrated, work log information is also included in the calculation.
Most Active Reviewers
This report shows the top five Reviewers in terms of the number of pull requests reviewed in the selected time period.
The reviewer analysis is also highlighted with more details in the contributor list.
Most Active Submitters
This report shows the top five Submitters in terms of the number of pull requests opened in the selected time period.
The submitter analysis is also highlighted with more details in the contributor list.
Most Productive Developers
This report shows the top five developers in terms of the impact they made with their code changes with a minimum churn rate.
In order to be a productive developer, the developer should have a high impact and low churn rate that indicates high complexity improvements in a more focused way.
Most Effective Languages
This metric reflects teams’ efficiency in different development languages. In this report, the focus is efficiency because understanding how efficiently the team is working in different languages would help you guide your teams to take the necessary steps to drive effectiveness in the languages the company is using.
The efficiency is highlighted in 3 categories in terms of percentage value;
- Low Efficiency: 0% - 69%
- Average Efficiency: 70% - 86%
- High Efficiency: 87% - 100%
Line of Codes by Days
This metric shows the progress in terms of the lines of code changes for each day.
We strongly recommend evaluating this report with other related metrics like code impact, efficiency, work focus, issue type, and more.