Automated Analytics for Remote Software Development
Take a Tour
The goal of Programeter service is to provide you with insightful understanding on your programming team's know-how, contribution, performance and activity based on contributed source code. This tour will guide you through indicators, measured aspects and sample reports that you would receive as a part of Programeter service.
Online DEMO
Catch a glimpse of what could be identified from your contributions! Join us for a demo and see how you can benchmark your results with your teammates.
How It Works?
What Aspects are Measured?
Distribution of Programmers Contribution Types
This chart gives insight into developer's programming style by illustrating diversity of his contribution.
Team benchmark
Team benchmark is the source of healthy competition inside the team. All members are positioned in order of their know-how score. Arrows
and 
indicate change direction compared to the previous values.
and indicate change direction compared to the previous values.Team Activity
Team activity chart illustrates trend in activity during the last 52 weeks and compares it to the average over the last year. Activity measures number of components and frequency of modifications made to them by the team:
Project Code Stability
Stability chart illustrates trends in stability of the project source code during last 52 weeks. Code is stable when it hasn't been changed for 2 weeks.
Contribution Trend
This chart illustrates size of contribution made by the developer during the last 12 months. Each bar shows amount of source code (and comments) written by the developer during the corresponding month
Know-How
Know-How chart illustrates trends in the developer's know-how throughout the project. The chart area is the total know-how of the developer in the project:
Contribution Size
Contribution size chart illustrates total contribution made by the developer throughout the project. Orange area depicts amount of source code commentaries:
Know-How Distribution
Illustration of the unique and shared know-how distribution between active team members and leaving members:
Knowledge of Leaving Team Member
Lists components of the software which are a part of leaving developer's unique know-how. Components are sorted in alphabetical order. For each component various know-how indicators are displayed: unique know-how illustrated developers unique knowledge in the component, shared know-how - knowledge shared with at least one active team member, team know-how - team total knowledge. Size of the component in source code statement. And most importantly there is a list of active developers with whom leaving member shares know-how in the particular component.Indicators
Know-How Indicators
- Know-How Score illustrates the breadth of the developer's knowledge in the project. The value is measured on the scale from 0 to 10. For example, the know-how score of 6.5 in certain project, means that developer is capable of working alone with most project components.
- Fresh Know-How represents the knowledge that was refreshed during the reporting period. For instance, if developer A has developed component "C" in the product and he has done changes to this component during last month, then it will be counted in his fresh know-how.
- New Know-How measures only knowledge that was introduced during the reporting period. For instance, if developer A has created new component "C" in the product during last month, then it will be counted in his new know-how.
- Unique Know-How similar to know-how score, but measures only knowledge that is NOT shared with other team members. For instance, if developer A has developed component "A" in the product and nobody else contributed to this component, then it will be counted in his unique know-how.
- Shared Know-How similar to know-how score, but measures only knowledge that is shared with other team members.
Contribution Indicators
- Contribution Size illustrates the size of code produced by the developer during the reporting period. Size is measured in lines of code and takes into account new lines added by the developer, lines that developer has modified and lines that he has deleted.
- New Code is the number of new lines of code that developer has added during the reporting period.
- Modified code is depicted by two indicators, namely "other" and "own". These indicators represent amount of lines of code modified by the developer during the reporting period. If the developer has modified a line of code created by someone else, then the indicator "other" is increased by one. And if he modifies a line created by himself, then the number "own" is increased accordingly.
- Deleted Code is traced in a same manner as modified code, by two indicators "other" and "own". They keep the count of lines of code deleted during the reporting period. Each deleted line increases either indicator "other" or "own". If developer deletes his own line of code then the indicator "own" is raised by one. If the deleted code was created by someone else, then the indicator "other" is raised consequently.
- Active Days illustrates the number of days when developer was making code contributions.
- Activity developer's or team's activity during 1 month. It measures the number of components and frequency of modifications made to them by the given developer (or team).
Quality of Contribution
- Density of Comments - ratio of comments to the total contribution of the developer. If developer contributes one line to the project then the total number of comments in the project is likely to change by this number.
- Team Friendliness illustrates how much the developer is oriented towards working together with other team members. The value is calculated using developer's shared and unique know-how and is measured on the scale from 0 to 10.
- Stability - At the given moment of time stability measures which part of the project source code remained unchanged for at least 3 months.
- Effort illustrates the size of the work developer has performed during the reporting period. Any code contribution (new code, modifications, deleting the code) is counted as effort.
- Efficiency illustrates the utility of the effort: how much of the effort translates into the code used in the project.
- Code Maturity illustrates how code contributed by the developer survives the test of time. Lower values mean that the produced code often needs to be corrected or adopted by other team members.
Reports
Programmer Performance Report
Performance Report is a monthly report which presents measurements of programmer's performance in a monthly period. This type of report is created for every single team member.
Team Performance Report
Team Performance Report indicates the overview of the whole team as a single unit. Contribution-related team performance trends are visualized in this type of report.
Programmer's Profile Report
Programmer's Profile Report contains performance metrics which reflects programmer's overall performance and knowledge of current project. This report aggregates all the metrics starting from the day one of the project.
Attrition report
Attrition report is used to inform which knowledge is possessed by a programmer who is leaving the project. Report explicitly shows what source code modules are a part of his knowledge. Additionally Attrition report suggests which programmer is most suited to take over the tasks of the person who is leaving. It also gives insight on what expertise will be lost for the project. Attrition reports are provided upon the request of the customer.
Team report is the source of objective insight into product development and is based upon know-how, activity and commitment indicators. Report consists of 2 parts. The first one contains information about each individual team member.