Development Behaviors

Status Overview

Status Overview aims to show developer 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 developer 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 developer 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 developer.

Experimenting

Developers 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 developers 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 developers 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 developers 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.