Teams

Analyzing Team Capability Across Time

Weekly KEDE for a team is calculated as follows:

1. A developer can be assigned to one or more teams. A team membership has a start and end date.
2. A developer commits to a repository. A repository can be assigned to a project.
3. We take all developers who belonged to a team for a selected time period and contributed code to any of the company's projects' repositories during the same, already selected time period.
4. For each developer Weekly KEDE is aggregated over all repositories. For example, if developer A contributed to repositories R1 and R2 during a week and Weekly KEDE for R1 was 2 and Weekly KEDE for R2 is 3 then the developers's Weekly KEDE would be 5 for that project for that week.

The same procedure is followed for Daily KEDE.

Analyzing the capability of a team is essential for understanding its productivity and efficiency. The diagram below presents a time series of a team's capability for a selected period across selected projects.

On the x-axis, you have the month dates, and on the y-axis, you have the weekly KEDE values. Each colored dot represents an individual developer's Weekly KEDE, and the dark blue line is the average weekly KEDE for all the developers in the team calculated by EWMA.

In addition, it's important to compare the team's performance with the average performance of the company. This is presented by the Weekly KEDE for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's Weekly KEDE is presented as a light gray dot, and the black line is the average weekly KEDE for those developers calculated by EWMA.

Furthermore to tracking the team's performance across all projects, it is also useful to analyze their capability on specific projects. For this, you can select the projects you want to analyze and view the Weekly KEDE for only those projects. The logic remains the same, with the only difference being that you're analyzing the team's performance on a subset of projects.

The same report can be run for Daily KEDE, providing a more granular view of the team's performance. Overall, analyzing the team's capability across time and projects is essential for improving productivity, identifying strengths and weaknesses, and making data-driven decisions to improve the team's performance.

Analyzing the Distribution of Team Capability

Along with the time series of the team's capability, it's very useful to see a histogram of the underlying frequency distribution. A frequency distribution shows how often each different value in a set of data occurs.

The diagram below presents a histogram of weekly averaged KEDE values for a selected period. On the x-axis, we have the Weekly KEDE, and on the y-axis, we have the percentage of each particular value.

Firstly, we are interested in the team's summarized historical capability. That is presented by the histogram in color of the Weekly KEDE frequency of the developers who were assigned to the team for the selected period. The blue vertical line is the average weekly KEDE for the team for the selected period, calculated by arithmetic mean. The median Weekly KEDE for the team for the selected period is presented by the green vertical dashed line.

Secondly, we are interested in the summarized historical capability of the company. That is presented by the histogram in gray of the Weekly KEDE frequency of all other company developers who contributed to all other company teams during the selected time period. The black vertical line is the average weekly KEDE of all other developers, calculated by arithmetic mean.

This report can also be run for Daily KEDE. Additionally, it's useful to show the capability of a team only across selected projects. The logic is the same, only this time we select Weekly KEDE only for the selected projects.

Analyzing Capability of Teams: Time Series and Frequency Distribution

Analyzing and comparing teams' capabilities to the company average can provide valuable insights for project and schedule management, as well as for identifying areas where teams may need additional resources or support. The diagram below presents a time series of Weekly KEDE values for two teams for a selected period across all projects.

Each team's average capability is presented by the dark blue line, while the black line represents the average weekly KEDE for the company as a whole. From the diagram, it can be observed that the first team's average capability is higher than the company average, indicating that they have been performing exceptionally well during the selected period. Conversely, the second team's average capability is less than the company average, suggesting that they may need further support to improve their performance.

Along with the time series of the capability of the teams, it's very useful to see histograms of the underlying frequency distributions. The diagram below presents histograms of weekly averaged KEDE values for the same two teams.

Each team's average capability is presented by the blue vertical line, and the median weekly KEDE for each team for the selected period is presented by the green vertical dashed line. The vertical black line represents the average weekly KEDE for the company. For the first team, both the median and the average capability are higher than the company average capability, while the median and average of the second team are less than the company average.

It's also possible to show the capability of teams only across selected projects using the same logic, selecting Weekly KEDE only for the selected projects. Furthermore, this report can also be generated for Daily KEDE.

Analyzing Team Happiness Over Time

Happiness level for a team is calculated as follows:

1. Take all developers who contributed code to any of the team's repositories during a selected time period.
2. For each developer, their Happiness level is computed by aggregating Happiness levels values over all repositories they contributed to during that week. For instance, if developer A contributed to repositories R1 and R2 during a week, and the Happiness level values for R1 and R2 were 20 and 30 respectively, then the developer's Happiness level for that team and week would be 50.

KEDEHub provides insights into team average happiness over time, allowing organizations to monitor and identify trends in their performance. The diagram below presents a time series of Happiness levels for a selected team over a given period. On the x-axis, the diagram displays the week dates, while on the y-axis, it shows the Happiness levels.

Each colored dot represents an individual developer's Happiness level, and the blue line represents the average Happiness level for all developers calculated by EWMA.

In addition, it's important to compare the team's happiness with the average happiness of the company. This is presented by the Weekly Happiness for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's Weekly Happiness is presented as a light gray dot, and the black line is the average weekly Happiness for those developers calculated by EWMA.

This report can be generated for Daily Happiness as well. Additionally, the same report can be run for multiple teams, allowing organizations to compare and analyze their team Happiness level across various initiatives.

Analyzing the Distribution of Team Happiness

In addition to tracking a team's Happiness level over time, it is also useful to examine the underlying frequency distribution of its Happiness levels. A frequency distribution provides insights into the distribution of the Happiness values and how often each value occurs.

The diagram below displays a histogram of averaged Happiness levels for a selected period, with the x-axis representing the Happiness level and the y-axis showing the percentage of each particular value.

Firstly, we are interested in the team's summarized historical Happiness. That is presented by the histogram in color of the Weekly Happiness frequency of the developers who were assigned to the team for the selected period. The blue vertical line is the average weekly Happiness for the team for the selected period, calculated by arithmetic mean. The median Weekly Happiness for the team for the selected period is presented by the green vertical dashed line.

Secondly, we are interested in the summarized historical Happiness of the company. That is presented by the histogram in gray of the Weekly Happiness frequency of all other company developers who contributed to all other company teams during the selected time period. The black vertical line is the average weekly Happiness of all other developers, calculated by arithmetic mean. The median Weekly Happiness for all other developers is presented by the red vertical dashed line.

This report can also be run for Daily Happiness. Additionally, it's useful to show the Happiness of a team only across selected projects. The logic is the same, only this time we select Weekly Happiness only for the selected projects.