New team
{{ team.team_name }}
{{team.team_name}}
New team
Description
Analyzing Company Capability Through Time
The diagram presents a time series of aggregated KEDE values for a whole company for a selected period, with the x-axis representing the week dates and the y-axis displaying the KEDE values.
Each individual developer's aggregated KEDE is presented as a colored dot on the diagram, providing a clear visual representation of how the company's capability changes over time. The dark blue line on the diagram represents the average KEDE for your developers, calculated using the Exponentially Weighted Moving Average (EWMA) method.
To gain a deeper understanding of your organization's capability, it's important to compare it to the capability of the industry as a whole. The same diagram presents the aggregated KEDE for all developers who contributed to all other companies on KEDEHub during the selected time period, with each individual developer's aggregated KEDE presented as a light gray dot. The black line on the diagram represents the average KEDE for those developers, calculated using EWMA.
Analyzing Company Capability Distribution
The diagram presents a histogram of aggregated KEDE values for a selected period, with the x-axis representing the KEDE and the y-axis displaying the percentage of each particular value.
The histogram is presented in color for the company's developers, with the blue vertical line representing the average KEDE for the selected period and the green vertical dashed line representing the median KEDE.
To gain a deeper understanding of the organization's capability levels, it's important to compare them with the industry averages. The same diagram presents the histogram in gray of the KEDE frequency of all other developers who contributed to all other companies on KEDEHub during the selected time period, with the black vertical line representing the average KEDE of all other developers.
Analyzing the Impact of Company Size on its Capability
The diagram is a time-series that displays how your organization's capability is affected by team size over time.
The x-axis of the diagram represents the dates, while the y-axis on the left displays the capability in KEDE values. The dark blue line on the diagram represents the average KEDE for all the developers who contributed to the company's projects in a given week, calculated using EWMA. This line provides a clear visual representation of how the organization's capability changes over time.
On the right side of the diagram, the y-axis displays the size of the company, represented by the number of developers who contributed to any of the company's projects in a given week. The green line on the diagram represents how the company size changes over time, with each point on the line representing the number of developers who contributed in a given week.
Analyzing the Distribution of Capability and Number of Developers
The histogram presents how the frequency distribution of company's capability changes with the number of developers over time.
The x-axis displays the number of developers who contributed to any of the projects in a given week, while the y-axis represents the KEDE values. Each individual developer's aggregated capability is presented as a light blue dot on the diagram, while the dark blue line represents the average capability for all developers calculated by arithmetic mean. Analyzing this histogram provides insight into how the capability of the company is affected by the number of developers who contribute to the projects.
Analyzing Company Happiness Over Time
The diagram below presents a time series of Happiness levels for the company 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 dark blue line represents the average Happiness level for all developers calculated by Exponentially Weighted Moving Average (EWMA) method.
Analyzing the Distribution of Company Happiness
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.
The histogram is presented in color with the blue vertical line representing the average Happiness level for the company for the selected period, calculated using arithmetic mean. The median Happiness level for the company for the selected period is presented by the green vertical dashed line.
Analyzing Company Information Loss Rate Over Time
The diagram company Rework (Information Loss Rate) over a selected period. On the x-axis, the diagram displays the week dates, while on the y-axis, it shows the waste levels.
Each colored dot represents an individual developer's waste level, and the dark blue line represents the average waste level for all developers calculated by EWMA.
Analyzing the Distribution of Company Information Loss Rate
The diagram below displays a histogram of averaged waste levels for a selected period, with the x-axis representing the waste level and the y-axis showing the percentage of each particular value.
The histogram is presented in color for the company, with the blue vertical line representing the average waste level for the company for the selected period, calculated using arithmetic mean. The median waste level for the company for the selected period is presented by the green vertical dashed line.
In the histogram visualization, values have been adjusted for clarity:
This method provides a clear representation by highlighting the distribution of the majority of the data. However, it's crucial for viewers to note that for visualization purposes, extreme values (below 1 or above 100) are grouped into their respective edge bins.
Analyzing a Developer's Capability Over Time
The diagram provides a time series of the capability of a developer for a selected period across all projects.
The x-axis displays the week dates, while the y-axis represents KEDE values. The blue dot on the diagram for each week represents the developer's capability. The dark blue line on the diagram represents the average KEDE for the developer, calculated using EWMA.
To compare the developer's capability with the average capability of the company, you can view the KEDE for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's capability is presented as a light gray dot, and the black line represents the average capability for those developers, calculated using EWMA.
Analyzing the Underlying Distribution of a Developer's Capability
The diagram presents a histogram of a developer's capability for a selected period.
On the x-axis, you have KEDE, and on the y-axis, you have the percentage of each particular value. First, the developer's summarized historical capability is presented by the histogram in color of the KEDE frequency for the selected period. The blue vertical line is the average capability for the developer for the selected period, calculated by arithmetic mean. The median capability for the developer for the selected period is presented by the green vertical dashed line.
Then, to compare the developer's capability with the company average, the summarized historical capability of all other company developers is presented by the gray histogram of KEDE frequency for all other company projects during the selected time period. The black vertical line is the average capability of all other developers, and the red vertical dashed line is the median capability of all other developers for the selected period.
Analyzing a Developer's Happiness Over Time
The diagram presents a time series of a developer's happiness for a selected period across all projects, allowing you to track their happiness levels over time and gain insights into what affects their work experience.
The x-axis of the diagram displays the dates, while the y-axis shows the happiness values. Each week's happiness level is represented by a blue dot on the diagram, giving you a clear visual representation of how the developer's happiness changes over time. Additionally, the dark blue line on the diagram represents the average happiness for the developer, calculated using the Exponentially Weighted Moving Average (EWMA) method. By analyzing this line, you can gain a deeper understanding of the overall trend of the developer's happiness levels over time.
But to gain a deeper understanding of a developer's happiness levels, it's important to compare them with the company averages. The Happiness diagram displays the happiness levels of all developers who contributed code to any company project during the selected time period. Each individual developer's happiness is represented by a light gray dot, while the average happiness calculated using EWMA is represented by a black line.
Analyzing the Underlying Distribution of a Developer's Happiness
The histogram presents the happiness values for a selected period, with the x-axis displaying the happiness and the y-axis showing the percentage of each particular value.
The histogram is presented in color for the developer, with the blue vertical line representing the average happiness level for the selected period and the green vertical dashed line representing the median happiness level.
To gain a deeper understanding of the developer's happiness levels, it's important to compare them with the company averages. The same histogram can be generated for all other developers who contributed to all other company projects during the selected time period, with the histogram presented in gray. The black vertical line represents the average happiness level for all other developers, while the red vertical dashed line represents the median happiness level.
Analyzing a Developer's Codnitive Load Over Time
The diagram presents a time series of a developer's Codnitive Load for a selected period across all projects, allowing you to track their Codnitive Load levels over time and gain insights into what affects their work experience.
The x-axis of the diagram displays the dates, while the y-axis shows the Codnitive Load values. Each week's Codnitive Load level is represented by a blue dot on the diagram, giving you a clear visual representation of how the developer's Codnitive Load changes over time. Additionally, the dark blue line on the diagram represents the average Codnitive Load for the developer, calculated using the Exponentially Weighted Moving Average (EWMA) method. By analyzing this line, you can gain a deeper understanding of the overall trend of the developer's Codnitive Load levels over time.
But to gain a deeper understanding of a developer's Codnitive Load levels, it's important to compare them with the company averages. The diagram displays the Codnitive Load levels of all developers who contributed code to any company project during the selected time period. Each individual developer's Codnitive Load is represented by a light gray dot, while the average Codnitive Load calculated using EWMA is represented by a black line.
In the time-series visualization, values have been adjusted for clarity:
This method provides a clear representation by emphasizing the main trend of the data over time. However, it's essential for viewers to note that, for visualization purposes, extreme values (below 1 or above 100) are capped at their respective bounds.
Analyzing the Underlying Distribution of a Developer's Codnitive Load
The histogram presents the Codnitive Load values for a selected period, with the x-axis displaying the Codnitive Load and the y-axis showing the percentage of each particular value.
The histogram is presented in color for the developer, with the blue vertical line representing the average Codnitive Load level for the selected period and the green vertical dashed line representing the median Codnitive Load level.
To gain a deeper understanding of the developer's Codnitive Load levels, it's important to compare them with the company averages. The same histogram can be generated for all other developers who contributed to all other company projects during the selected time period, with the histogram presented in gray. The black vertical line represents the average Codnitive Load level for all other developers, while the red vertical dashed line represents the median Codnitive Load level.
In the histogram visualization, values have been adjusted for clarity:
This method provides a clear representation by highlighting the distribution of the majority of the data. However, it's crucial for viewers to note that for visualization purposes, extreme values (below 1 or above 100) are grouped into their respective edge bins.
Analyzing Project Capability Over Time
The diagram presents a time series of KEDE values for a selected project over a given period. On the x-axis, the diagram displays the week dates, while on the y-axis, it shows the KEDE values.
Each colored dot represents an individual developer's KEDE, and the dark blue line represents the average KEDE for all developers calculated by EWMA.
To gain a deeper understanding of the organization's project capability, it's important to compare it with the capability of all other projects. The same diagram displays the KEDE of all developers who contributed to other company projects during the selected time period, with each such individual developer's KEDE presented as a light gray dot, and the black line representing the average KEDE for those developers calculated by EWMA.
Additionally, the same report can be run for multiple projects, allowing organizations to compare and analyze their project capability across various initiatives.
Analyzing the Distribution of Project Capability
The diagram displays a histogram of averaged KEDE values for a selected period, with the x-axis representing the KEDE and the y-axis showing the percentage of each particular value.
The histogram is presented in color for the selected project, with the blue vertical line representing the average KEDE for the project for the selected period, calculated using arithmetic mean. The median KEDE for the project for the selected period is presented by the green vertical dashed line.
To gain a better understanding of the project's capability levels, it's important to compare them with those of other projects in the company. The same diagram presents the KEDE frequency of all other company developers who contributed to all other projects during the selected time period, with the histogram presented in gray. The black vertical line represents the average KEDE of all other developers calculated by arithmetic mean. The same report can also be run for Daly KEDE and for multiple projects.
Analyzing Project Happiness Over Time
The diagram presents a time series of Happiness level for a selected project over a given period. On the x-axis, the diagram displays the week dates, while on the y-axis, it shows the Happiness level.
Each colored dot represents an individual developer's Happiness level, and the dark blue line represents the average Happiness level for all developers calculated by EWMA. To see the individual dots you need to select 'verbose' from the diagram options.
In addition, it's important to compare the project's happiness with the average happiness of the company. To do this you need to select 'compare' from the diagram options. Now is presented the happiness for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's happiness is presented as a light gray dot, and the black line is the average happiness for those developers calculated by EWMA. To see the individual dots you need to select 'verbose' from the diagram options.
Additionally, the same report can be run for multiple projects, allowing organizations to compare and analyze their project happiness across various initiatives.
Analyzing the Distribution of Project Happiness level
The diagram displays a histogram of averaged Happiness level for a selected period, with the x-axis representing the Happiness level and the y-axis showing the percentage of each particular value.
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. To see the individual dots you need to select 'verbose' from the diagram options.
In addition, it's important to compare the project's happiness with the average happiness of the company. To do this you need to select 'compare' from the diagram options. This is presented by the Happiness for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's Happiness is presented as a light gray dot, and the black line is the average Happiness for those developers calculated by EWMA. The median Weekly Happiness for all other developers is presented by the red vertical dashed line. To see the individual dots you need to select 'verbose' from the diagram options.
This report can be generated for Daily Happiness as well. Additionally, the same report can be run for multiple projects, allowing organizations to compare and analyze their project Happiness level across various initiatives.
Analyzing Project Information Loss Rate Over Time
The diagram presents a time series of waste level for a selected project over a given period. On the x-axis, the diagram displays the week dates, while on the y-axis, it shows the waste level.
Each colored dot represents an individual developer's waste level, and the dark blue line represents the average waste level for all developers calculated by EWMA.
In addition, it's important to compare the project's waste with the average waste of the company. To do this you need to select 'compare' from the diagram options. Now is presented the waste for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's waste is presented as a light gray dot, and the black line is the average waste for those developers calculated by EWMA. To see the individual dots you need to select 'verbose' from the diagram options.
Additionally, the same report can be run for multiple projects, allowing organizations to compare and analyze their project waste across various initiatives.
Analyzing the Distribution of Project Information Loss Rate
The diagram displays a histogram of averaged waste level for a selected period, with the x-axis representing the waste level and the y-axis showing the percentage of each particular value.
The histogram is presented in color for the selected project, with the blue vertical line representing the average waste level for the project for the selected period, calculated using arithmetic mean. The median waste level for the project for the selected period is presented by the green vertical dashed line. To see the individual dots you need to select 'verbose' from the diagram options.
In addition, it's important to compare the project's waste with the average waste of the company. To do this you need to select 'compare' from the diagram options. This is presented by the waste for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's waste is presented as a light gray dot, and the black line is the average waste for those developers calculated by EWMA. The median Weekly waste for all other developers is presented by the red vertical dashed line. To see the individual dots you need to select 'verbose' from the diagram options.
The same report can also be run for Daly KEDE and for multiple projects.
In the histogram visualization, values have been adjusted for clarity:
This method provides a clear representation by highlighting the distribution of the majority of the data. However, it's crucial for viewers to note that for visualization purposes, extreme values (below 1 or above 100) are grouped into their respective edge bins.
Analyzing the Relationship Between Project Size and Capability
The diagram is a time-series chart that shows how project capability is affected by project size over time. The x-axis displays the week dates, while the two y-axes represent the capability and size of the project.
The capability axis, located on the left, is measured in KEDE values and is represented by a dark blue line calculated using the Exponentially Weighted Moving Average (EWMA) method. Each point on the blue line represents the average KEDE for all developers who contributed in that week. On the right, the project size axis is represented by a green line that shows the number of developers who contributed to the project in a given week.
Analyzing the Optimal Project Size
The diagram shows the project size that achieved the highest averaged KEDE values for a selected period.
On the x-axis, we have the number of developers who contributed to the project in a given week. On the y-axis, we have the percentage of each particular value. Each individual developer's aggregated capability is represented as a light blue dot on the diagram. The dark blue line is the average capability for all developers, calculated by arithmetic mean.
Analyzing Team Capability Across Time
The diagram 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 KEDE values. Each colored dot represents an individual developer's KEDE, and the dark blue line is the average KEDE for all the developers in the team calculated by EWMA. To see the individual dots you need to select 'verbose' from the diagram options.
In addition, it's important to compare the team's performance with the average performance of the company. To do this you need to select 'compare' from the diagram options. Now is presented the KEDE for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's KEDE is presented as a light gray dot, and the black line is the average KEDE for those developers calculated by EWMA. To see the individual dots you need to select 'verbose' from the diagram options.
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 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.
Analyzing the Distribution of Team Capability
The diagram presents a histogram of averaged KEDE values for a selected period. On the x-axis, we have the 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 KEDE frequency of the developers who were assigned to the team for the selected period. The blue vertical line is the average KEDE for the team for the selected period, calculated by arithmetic mean. The median KEDE for the team for the selected period is presented by the green vertical dashed line.
Secondly, we are interested in comparing the team with the summarized historical capability of the company. To do this you need to select 'compare' from the diagram options. That is presented by the histogram in gray of the 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 KEDE of all other developers, calculated by arithmetic mean.
Analyzing Team Happiness Over Time
The diagram 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. To see the individual dots you need to select 'verbose' from the diagram options.
In addition, it's important to compare the team's happiness with the average happiness of the company. To do this you need to select 'compare' from the diagram options. This is presented by the Happiness for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's Happiness is presented as a light gray dot, and the black line is the average Happiness for those developers calculated by EWMA. The median Weekly Happiness for all other developers is presented by the red vertical dashed line. To see the individual dots you need to select 'verbose' from the diagram options.
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
The diagram 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 Happiness frequency of the developers who were assigned to the team for the selected period. The blue vertical line is the average Happiness for the team for the selected period, calculated by arithmetic mean. The median Happiness for the team for the selected period is presented by the green vertical dashed line.
Secondly, we are interested in comparing the team with the summarized historical Happiness of the company. To do this you need to select 'compare' from the diagram options. That is presented by the histogram in gray of the 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 Happiness of all other developers, calculated by arithmetic mean. he median Happiness for all other developers is presented by the red vertical dashed line.
Analyzing the Relationship Between Team Size and Capability
The diagram is a time-series chart that shows how team capability is affected by team size over time. The x-axis displays the week dates, while the two y-axes represent the capability and size of the team.
The capability axis, located on the left, is measured in KEDE values and is represented by a dark blue line calculated using the Exponentially Weighted Moving Average (EWMA) method. Each point on the blue line represents the average KEDE for all developers who contributed in that week. On the right, the team size axis is represented by a green line that shows the number of developers who contributed to the team in a given week.
Analyzing the Optimal Team Size
The diagram shows the team size that achieved the highest averaged KEDE values for a selected period.
On the x-axis, we have the number of developers who contributed to the team in a given week. On the y-axis, we have the percentage of each particular value. Each individual developer's aggregated capability is represented as a light blue dot on the diagram. The dark blue line is the average capability for all developers, calculated by arithmetic mean.
Analyzing Team Information Loss Rate Over Time
The diagram presents a time series of waste level 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 waste level.
Each colored dot represents an individual developer's waste level, and the dark blue line represents the average waste level for all developers calculated by EWMA.
In addition, it's important to compare the team's waste with the average waste of the company. To do this you need to select 'compare' from the diagram options. Now is presented the waste for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's waste is presented as a light gray dot, and the black line is the average waste for those developers calculated by EWMA. To see the individual dots you need to select 'verbose' from the diagram options.
Additionally, the same report can be run for multiple teams, allowing organizations to compare and analyze their project waste across various initiatives.
Analyzing the Distribution of Tean Information Loss Rate
The diagram displays a histogram of averaged waste level for a selected period, with the x-axis representing the waste level and the y-axis showing the percentage of each particular value.
The histogram is presented in color for the selected team, with the blue vertical line representing the average waste level for the team for the selected period, calculated using arithmetic mean. The median waste level for the team for the selected period is presented by the green vertical dashed line. To see the individual dots you need to select 'verbose' from the diagram options.
In addition, it's important to compare the team's waste with the average waste of the company. To do this you need to select 'compare' from the diagram options. This is presented by the waste for all developers who contributed code to any of the company projects during the selected time period. Each individual developer's waste is presented as a light gray dot, and the black line is the average waste for those developers calculated by EWMA. The median Weekly waste for all other developers is presented by the red vertical dashed line. To see the individual dots you need to select 'verbose' from the diagram options.
The same report can also be run for Daly KEDE and for multiple teams.
In the histogram visualization, values have been adjusted for clarity:
This method provides a clear representation by highlighting the distribution of the majority of the data. However, it's crucial for viewers to note that for visualization purposes, extreme values (below 1 or above 100) are grouped into their respective edge bins.
Analyzing Capability per Developer on Selected Team
To gain deeper insight into the contribution of individual developers to a team's capability, the chartpresents the capability of the team over a time period, broken down by the individual developers who contributed to the team during that time.
On the x-axis, we have the week dates, and on the y-axis, we have the KEDE values. The chart displays a series of stacked bars, with each bar representing the KEDE for the selected team. Each bar is divided into multiple boxes, with each box corresponding to the fraction of KEDE contributed by a specific software developer. The legend lists all the developers who contributed to the selected team, and the colors in each bar indicate which developer made each contribution.
By using this chart, it is possible to identify which developers had the greatest impact on the team's capability during a given week or time period. This information can help organizations to optimize their development teams and assign tasks more effectively, ultimately improving team outcomes.
Analyzing Capability per Developer on Selected Project
To gain deeper insight into the contribution of individual developers to a project's capability, the chartpresents the capability of the project over a time period, broken down by the individual developers who contributed to the project during that time.
On the x-axis, we have the week dates, and on the y-axis, we have the KEDE values. The chart displays a series of stacked bars, with each bar representing the KEDE for the selected project. Each bar is divided into multiple boxes, with each box corresponding to the fraction of KEDE contributed by a specific software developer. The legend lists all the developers who contributed to the selected project, and the colors in each bar indicate which developer made each contribution.
By using this chart, it is possible to identify which developers had the greatest impact on the project's capability during a given week or time period. This information can help organizations to optimize their development teams and assign tasks more effectively, ultimately improving project outcomes.
Analyzing Predictability of Selected Project
We measure the predictability of a software development project as its ability to meet its expected knowledge discovery rate within a set timeframe. The learning curve shows the rate of knowledge accumulation about "what to do" and "how to do it" in order to deliver working software. By comparing the rate of knowledge acquisition of the current project with that of the forecasted learning curve, we can gauge how closely the process aligns with our expectations The learning curve serves as a leading indicator for project predictability by measuring the rate of knowledge acquisition, enabling proactive management of potential issues and alignment with project expectations.
On the x-axis we have weekly dates from the start of a project, while on the y-axis we have the predictability index \(P\) for each week. The predictability index \(P\) ranges from 0 to 100. A predictability index of 100 indicates that the new project is perfectly aligned with the forecast, while a predictability index of 0 suggests that the new project is significantly diverging from the forecast. The legend lists the selected projects.
By monitoring the predictability index over time, project managers can identify early signs of potential issues and take corrective actions to realign the project with the forecasted learning trajectory.
Analyzing the Distribution of a Developer's Capability across Projects
The diagram presents a stacked bar chart that allows for a detailed analysis of numeric values across two categorical variables. In this case, the first category is the developer's KEDE, and the second category is the projects the developer worked on during the selected time period.
On the x-axis, we have the week dates, and on the y-axis, we have the KEDE. Each bar represents the KEDE of the selected developer divided into a number of boxes, each corresponding to the fraction of the KEDE that the developer contributed to a particular project. This allows for a clear visualization of the developer's capability distribution across different projects.
Analyzing the Capability Distribution of a Developer Across Projects
The diagram presents a histogram of averaged KEDE values for a selected period, where each project that the developer worked on is presented in a different color.
his way, we have several histograms, one for each of the projects the developer contributed to. The red vertical line represents the average capability for the developer, while the green vertical dashed line represents the median capability.
Analyzing the Distribution of a Developer's Happiness across Projects
The diagram presents a stacked bar chart that allows you to look at numeric values across two categorical variables. The first category is the developer's happiness, and the second category is the projects that the developer worked on during the selected time period. Each bar on the chart represents the happiness of the selected developer, divided into a number of boxes, each one corresponding to the happiness that the developer felt on a particular project.
The x-axis of the chart displays the dates, while the y-axis shows the happiness levels. By analyzing the chart, you can gain insights into how a developer's happiness levels vary across different projects and identify any patterns or trends that may be affecting their mood.
Analyzing Developer Happiness Distributions Across Projects
The histogram presents a visualization of the averaged happiness values for a selected period, with the x-axis representing the happiness and the y-axis displaying the percentage of each particular value.
Each project that the developer worked on is represented with a different color, resulting in several histograms, one for each project. The red vertical line represents the average happiness for the developer, while the green vertical dashed line represents the median happiness level.
Analyzing the Distribution of a Developer's Cognitive Load across Projects
The diagram presents a stacked bar chart that allows you to look at numeric values across two categorical variables. The first category is the developer's cognitive load, and the second category is the projects that the developer worked on during the selected time period. Each bar on the chart represents the cognitive load of the selected developer, divided into a number of boxes, each one corresponding to the cognitive load that the developer felt on a particular project.
The x-axis of the chart displays the dates, while the y-axis shows the cognitive load levels. By analyzing the chart, you can gain insights into how a developer's cognitive load levels vary across different projects and identify any patterns or trends that may be affecting their mood.
Analyzing Developer Cognitive Load Distributions Across Projects
The histogram presents a visualization of the averaged cognitive load values for a selected period, with the x-axis representing the cognitive load and the y-axis displaying the percentage of each particular value.
Each project that the developer worked on is represented with a different color, resulting in several histograms, one for each project. The red vertical line represents the average cognitive load for the developer, while the green vertical dashed line represents the median cognitive load level.
Analyzing the Rework by a Developer Across Projects
Along with the capability of a developer, it's important to also analyze the rework they did across different projects. The diagram presents a stacked bar chart that shows how rework for a developer is distributed across different projects.
The x-axis shows the week dates and the y-axis shows the amount of bits of information lost per week. Lost information represents the knowledge that was initially perceived to be gained but turned out to be incorrect or misleading. Information loss rate is the ratio of lost information to the total perceived missing information. These metrics align with a knowledge-centric standpoint, where the focus is on the efficient use and management of knowledge. Each bar represents the bits lost by the selected developer, which is further divided into boxes. Each box corresponds to the fraction of bits lost by the developer for a particular project. The color of each box represents a different project. This way, we have a clear visualization of how much bits of information the developer replaced for each project during the selected time period.
Analyzing Cumulative Growth Rate of Knowledge Discovered per Developer on a Project
In the context of our knowledge-centric approach to software development, understanding the individual growth rates of knowledge discovered per developer is an important metric to track the progress of a project. The diagram below shows the exponential cumulative growth rates of each developer who worked on the selected project for a selected period.
The x-axis represents the week dates, while the y-axis represents the exponential cumulative growth rate. This quantifies the compound growth rate of knowledge discovered over time, taking into account the compounding effect of growth. It serves as a measure of how rapidly the knowledge of each developer is expanding.
The diagram uses a series of stacked bars to represent the exponential cumulative growth rate of knowledge for each developer, week by week. Each developer is depicted in a different color, allowing for clear differentiation between developers. A legend accompanying the diagram identifies the corresponding developer for each color.
Each bar is divided into multiple boxes, and these boxes collectively form a "virtual line" for each developer. Each virtual line corresponds to an individual developer's growth rate. The height of the line signifies the amount of knowledge a developer needed to discover, reflecting the knowledge gap between the required knowledge for project tasks and the knowledge the developer initially possessed.
This report is also available for Daily KEDE and for multiple projects. By running this report on multiple projects, you can compare the cumulative growth rate of developers across different projects and identify patterns and trends that may affect the success of your projects.
The visualization of the Cumulative Growth Rate of Knowledge Discovered in this format offers a valuable perspective on individual and collective learning within the project. By analyzing the individual lines, one can ascertain the rate of knowledge acquisition for each developer. Comparing the virtual lines helps in identifying variations in learning pace and potential areas where knowledge sharing or additional training might be beneficial.
This diagram, therefore, serves as a powerful tool for project managers and team leads, assisting in understanding the learning dynamics of the team and making informed decisions to guide the project's success.
Analyzing Growth Rates of Languages Used in a Project
In software development projects, it is common to use multiple programming languages. The diagram provides insight into the growth rates of each language used in the selected project for the selected period.
On the x-axis, we have the week dates, and on the y-axis, we have an exponential cumulative growth rate. Each bar represents the exponential cumulative growth rate of a language for the respective week, and the data for each of the languages is stacked so that we can see the total language growth rate for the selected project and time period. This diagram helps to understand how each language used in the project contributes to the overall growth rate.
Invite new company user
Analyzing Cumulative Growth of Knowledge Discovered on a Project
The cumulative growth of knowledge discovered is an important metric to track the progress of a project. The line on the diagram represents the growth of knowledge discovered during the selected period.
The x-axis represents the week dates, while the y-axis represents the knowledge discovered in bits of information.
Knowledge discovered is the cumulative sum of missing information (or questions, in our model) over a specific time period. It signifies the total amount of information contained in a set of messages, which is derived from the sum of the information in each individual message. By analyzing the growth rate of a project over time, you can gain insight into the performance of your team and the progress of the project.
Analyzing Cumulative Growth Rate of Knowledge Discovered on a Project
The cumulative growth rate of knowledge discovered is an important metric to track the progress of a project. The line on the diagram represents the cumulative exponential growth rate for all developera for the selected period.
The x-axis represents the dates, while the y-axis represents the exponential cumulative growth rate.
The exponential cumulative growth rate is a measure of the compound growth rate of knowledge discovered over time, which takes into account the compounding effect of growth. By analyzing the growth rate of a project over time, you can gain insight into the performance of your team and the progress of the project.
Forecasting Project Completion Time
KEDEHub utilizes a probabilistic forecasting approach, generating multiple possible future scenarios for a project. Each scenario depicts a unique pathway in which the project's knowledge discovery could progress.
On the forecast graph, the thick blue line represents the cumulative growth rate of the knowledge expected to be discovered for the successful delivery of the project. The x-axis displays the timeline of the new forecasted project, and the y-axis shows the cumulative growth of the knowledge to be discovered
The green line represents the most likely completion date, the dashed red line indicates the earliest possible completion date, and the dashed blue line designates the latest possible completion date. This range of outcomes helps you prepare for different eventualities and plan your project more effectively.
Clustering Projects by Cumulative Growth Rate of Knowledge Discovered
In order to implement Step 3 of Reference Class Forecasting (RCF), we nned to compare the CRT time series for projects to see they belong to the same reference class.
The diagram is a line plot displaying all the project curves together. The x-axis represents the number of weeks, while the y-axis represents the cumulative growth rate (CR).
To compare multiple Cumulative Return Time (CRT) curves in terms of their similarity, we use Dynamic Time Warping (DTW) to measure the similarity between them, considering their different time units.
The DTW distances between the curves are then used to perform hierarchical clustering, which groups the curves into clusters based on their similarity. Each cluster is then assigned a unique color, allowing users to easily identify which curves are closely related.
| Project | Predictability | Allocation | Process Quality | |||||
|---|---|---|---|---|---|---|---|---|
| {{ project.project.long_name }} {{ project.project.description }} |
{{ project.predictability }} |
{{ project['perc-allocation'] }} %
|
{{ project.allocation }} |
${{ project.cost }}K |
|
|
|
{{ project['cognitive-load'] }} |