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

​
Overview

Note that you are only seeing the performance of one contributor, selected in Filters. To change the contributor and see its corresponding data, please select the desired contributor 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 Contributor’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 contributor’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 individual contributor 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 contributor balances innovation with ongoing improvements. A rising trend indicates increasing productivity, while fluctuations may reflect shifts in priorities, technical debt reduction, or process optimizations.

For better understanding of Effective Output measurement, the graph includes color-coded indicators that show the engineer’s productivity levels during the selected time period, ranging from low to normal and excellent. A median engineer typically delivers 5–20 output units per month, helping to set benchmarks for productivity.

​
Output Breakdown

Overview: This bar chart displays the individual contributor’s 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. For better understanding of Output Breakdown measurement, the graph includes color-coded indicators that show the levels during the selected time period, ranging from low to normal and excellent.

​
Waste Rate

Overview: This line chart displays the Waste Rate, showing the proportion of output that has been removed, reworked, or refactored.
The Waste Rate graph measures the proportion of output in % 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 rate can never be lower than 0 and bigger than 100%. Deletions are tracked and visualized in other charts within the dashboard. This chart helps identify inefficiencies and areas for improvement in the development process.

​
Total Output Breakdown

Overview: This bar chart displays the total output breakdown for the selected contributor 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.

​
Top Repositories by Contribution

Overview: This table chart ranks repositories by individual’s 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 by the individual contributor during the analyzed period. Repositories are ranked based on several factors, including technology used, effective output, total output, and size increase. 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 table chart displays the effective output of selected contributor over the selected period, using color gradients to highlight productivity trends and fluctuations across the analyzed period.
The Effective Output Heatmap visualizes the effective output of selected contributor 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 team performance and areas for improvement.

​
Commits Heatmap

Overview: The table chart presents a detailed overview of total commits made by selected contributor over the selected period, showing absolute counts.
The Commits Heatmap visualizes the number of commits made by selected contributor over time, using color gradients to highlight contribution trends. This chart provides insights into constributor’s activity, showing periods of high and low commitment to the codebase, and helping to identify patterns in contribution frequency. 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.

​
Quality Score

Contact us at support@p10y.com.
⌘I