Development Behaviors

Status Overview

Status Overview aims to show contributor statuses based on the following two parameters;

• Impact: The code impact after any code change is calculated with various variables.
• Churn: The amount of code being modified shortly after the development.

When there is a contributor on the left side of the graph, especially on the ‘Could Be Stuck’ section, it should be carefully investigated because they may require some assistance to overcome their issues.

Could Be Stuck

If a contributor is in this section, it is possible that they require some help to handle the corresponding feature. When the status is repeating we strongly suggest taking the necessary steps before the situation becomes too overwhelming for the contributor.

Experimenting

Contributors in the experimenting section might be finding new perspectives, working on new features/technologies/languages, or experimenting for a breakthrough. 

It may also mean that the requirements and specifications in the analysis period were not clearly defined so which is why the churn rate is high.

Polishing

This section shows the contributors with low impact on the code base with a minimum churn. 

Therefore, it would be more likely to see team leaders, senior contributors and similar roles in this section because while having a higher skill set and more experience with the product to make any changes last longing, they are more likely to have less code impact because they mostly guide the team members and focus on the leading.

Otherwise, it may mean that contributors remaining in this area contribute to the project by working on smaller tasks. Depending on their output, it may be time to assign these individuals larger-scale tasks.

Prolific

The contributors in this section make a great contribution with a high impact and a low churn ratio. As long as they are working on the correct development the best practice would be to let them continue the development they are working on.

Regular Commits By Date

This report provides insights into the commit activity within the project, showing how frequently contributors are committing code to the repository. This report helps track productivity, identify patterns, and optimize team workflows by highlighting key commit-related metrics. By tracking when and how often code is being committed, teams can optimize workflows, anticipate code review needs, and spot potential bottlenecks early. This data also supports capacity planning and can drive discussions around improving team efficiency.

In this chart, you can see total commits and average number of commits per day. By using this data, you can track workload of your team and spot bottlenecks easily.

Average Commits displays the average number of commits made per developer over a given period. Tracking average allows teams to identify trends and assess whether development activities are increasing, decreasing, or remaining stable over time. It's useful for sprint planning and long-term project forecasting.

Daily Average Commits shows the average number of commits made per day across all contributors. Monitoring daily commit activity helps to identify whether work is evenly distributed throughout the week or concentrated on particular days. It can indicate whether workflows are consistent or if bottlenecks or crunch periods are occurring.

Most Frequent Commit Times identifies the times of day when commits are most frequently made to the repository. Understanding commit times is valuable for scheduling activities like code reviews, deployments, or collaborative coding efforts. It can also highlight peak working hours and inform decisions around developer availability and team synchronization.