This section describes the insights available for each chart on the Team (Beta) level. These include detailed information behind each chart, helping you understand the data and the metrics being displayed.

​
Overview

Before proceeding, please make sure you have created teams on the Teams page.

Note that you are only seeing the performance of one team, selected in Filters. To change the team and see its corresponding data, please select the desired team in the top-right corner of the Filters section.

Once you enable the metrics on the Repositories page, our tool and algorithm will process the essential data related to Team’s productivity.

The results will be displayed as Effective Output Units in graphs. These units represent the estimated values derived from the data we retrieved from commits.

Data shown in dashboards excludes contributors and commits that fall below a minimum average number of commits per month by contributor across all repositories over the entire time period. The default threshold is set to 5 commits per month, but this can be customized in the Settings >> Organization section.

​
Customizing Charts

All charts can be customized to suit your specific needs. Click the “Filters” button in the top-right corner of the Dashboards to access customization options. Note that you need to press the “Apply” button to apply the selected filters. For more information about filters, please visit the Dashboards page.

Additionally, you can compare the current period with the previous one by turning on the toggle, allowing for a clearer analysis of trends and progress over time.

​
Charts Explained

​
Effective Output

Overview: This line chart displays the selected team’s Effective Output over time, measured in output units. It includes both New Functionality and Refactored Functionality and can be viewed by day, week, month, quarter, or year.

The Effective Output graph visually represents the total productive output of the team over time, measured in output units. It combines two key components:

  • New Functionality – Code that introduces brand-new features.
  • Refactored Functionality – Improvements or modifications made to existing functionality that was originally deployed more than three weeks ago.

By tracking these two elements, the graph provides insight into how the team balances innovation with ongoing improvements. A rising trend indicates increasing productivity, while fluctuations may reflect shifts in priorities, technical debt reduction, or process optimizations.

This visualization helps teams assess their development efficiency and maintain a balance between building new features and refining existing ones.

​
Effective Output per Contributor

Overview: This line chart displays the Effective Output per Contributor over time, measured in output units. It includes both New Functionality and Refactored Functionality and can be viewed by day, week, month, quarter, or year.

The Effective Output per Contributor graph measures the total productive output of the selected team per contributor over time, expressed in output units. It consists of two key components:

  • New Functionality – Code that introduces brand-new features.

  • Refactored Functionality – Improvements or modifications made to existing functionality that was originally deployed more than three weeks ago.

This chart provides insight into how output is distributed across contributors within the selected team. A median engineer typically delivers 5–20 output units per month, helping to set benchmarks for productivity. Trends over time can highlight team efficiency, workload distribution, and areas for potential improvement.

​
Output Breakdown

Overview: This bar chart displays the engineering output breakdown by contribution type over a specified period, grouped by day, week, month, quarter, or year. It categorizes output into Added, Removed, Reworked, and Refactored functionality.

The Output Breakdown graph categorizes engineering output based on the type of contribution, providing a detailed view of how work is distributed. The four key contribution types are:

  • Added – New functionality introduced to the codebase.

  • Removed – Functionality that has been deleted.

  • Reworked – Changes made within 3 weeks of the original release.

  • Refactored – Changes made after 3 weeks of the original release.

This breakdown helps teams analyze development patterns, track the balance between innovation and maintenance, and identify trends in engineering effort over time.

​
Contributor Average Output Breakdown

Overview: This bar chart displays the monthly average engineering output per contributor in the selected team, categorized by contribution type. Output is averaged per active month, allowing for direct comparison across contributors.

The graph displays the monthly average engineering output per contributor, categorized by contribution type. It includes:

  • Added – New functionality introduced.

  • Removed – Functionality that has been deleted.

  • Reworked – Changes made within 3 weeks of release.

  • Refactored – Changes made after 3 weeks of release.

Output values are averaged per active months, enabling direct comparisons across all active contributors in the selected team. This graph helps assess productivity trends, contributor efficiency, and the distribution of engineering efforts.

​
Waste Ratio

Overview: This line chart displays the Waste Ratio, showing the proportion of output that has been removed, reworked, or refactored.

The Waste Ratio graph measures the proportion of output that has been removed, reworked, or refactored relative to the total output. A lower value is better, indicating more efficient and productive engineering work.

The waste ratio can never be lower than 1, and values below zero (deletions) are not shown. Deletions are tracked and visualized in other charts within the dashboard.

This chart helps identify inefficiencies and areas for improvement in the development process.

​
Contributor Waste Ratio

Overview: This bar chart displays the Waste Ratio per contributor in the selected team, showing the proportion of output that has been removed, reworked, or refactored. A lower value indicates more efficient output, with values not falling below 1.

The Contributor Waste Ratio graph measures the proportion of output that has been removed, reworked, or refactored for each contributor in the selected team. A lower value is better, reflecting higher efficiency and less unnecessary modification.

This chart allows for comparison of waste ratios across contributors in one team, helping to identify areas for process improvement.

​
Total Output Breakdown

Overview: This bar chart displays the total output breakdown for the selected team in analyzed period, categorized by Added, Removed, Reworked, and Refactored functionality. It highlights the distribution of engineering efforts across different contribution types.

The Total Output Breakdown graph provides a detailed view of the overall output during the analyzed period, categorized by contribution type:

  • Added – New functionality introduced.

  • Removed – Functionality that has been deleted.

  • Reworked – Changes made within 3 weeks of release.

  • Refactored – Changes made after 3 weeks of release.

This breakdown helps to understand the distribution of engineering efforts, providing insights into innovation, maintenance, and technical debt management across the organization.

​
Active Contributors

Overview: This line chart displays the absolute number of active contributors in the selected team—those who were committing to the codebase—over a specified period, grouped by day, week, month, quarter, or year.

The Active Contributors graph shows the number of contributors who have actively made commits to the codebase during each time period. It provides insight into team engagement and the distribution of contributions, helping to assess the level of participation over time.

​
Top Repositories by Contribution

Overview: This bar chart ranks repositories by contribution in the analyzed period, based on several factors. It highlights the most active and impactful repositories.

The Top Repositories by Contribution graph presents a ranked list of repositories that received contributions during the analyzed period.

Repositories are ranked based on several factors, including technology used, effective output, total output, size increase, and waste ratio.

This chart provides insights into which repositories saw the most activity and highlights areas of focus, efficiency, and growth across the team’s codebase.

​
Effective Output Heatmap

Overview: This heatmap displays the effective output of each contributor in the selected team over time, using color gradients to highlight productivity trends and fluctuations across the analyzed period.

The Effective Output Heatmap visualizes the effective output of each contributor in the selected over time, providing a clear view of productivity trends. It uses color gradients to highlight periods of high and low output, helping to identify patterns in contributors performance and areas for improvement.

This chart allows for easy comparison across contributors in the team, showing how output fluctuates throughout the analyzed period.

​
Commits Heatmap

Overview: The table chart presents a detailed overview of total commits made by contributors in the selected team over the selected period, showing absolute counts and sums for each contributor. Each row represents a different contributor, showing the total commit estimates for that team.

The Commits Heatmap visualizes the number of commits made by each contributor in the selected team over time, using color gradients to highlight contribution trends. This chart provides insights into team activity, showing periods of high and low commitment to the codebase, and helping to identify patterns in contribution frequency across different contributors.

Please note that you may notice some periods with missing data in the User Interface. This occurs when there are no commits during the selected period and with the applied filters.

Contact us at support@p10y.com.