Take a Tour

EyeQ - Take a Tour

This tour will guide you through sample reports that you may enjoy every month if you apply for our new and unique EyeQ service.

Monthly Performance Report

Monthly performance report is the source of objective insight into product development team performance and is based upon know-how, activity and commitment indicators. Report consists of 2 parts: the first part provides overall team performance information for the given month and the second one contains information about each individual team member.

Team Benchmark

Team benchmark is the source of healthy competition inside the team. All members are positioned in order of their monthly contribution size. Arrows 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.

Developer Profile

Developer profile is intended to be used to get the detailed picture on of each developer. It aggregates the KPIs over the whole history of programmers contribution.

Developer Individual KPIs

KPIs of each individual member of the team are summarized in the table. Each indicator contains both value for the member and average value for the whole team.

• Contribution size - illustrates the amount of code produced by the developer. Size is measured in non-commenting source code statements (NCSS). The value is independent of source code formatting style and depends on the programming language syntax.
• Activity of the developer - measures the number of components and frequency of modifications made to them by the given developer.
• Know-how score - illustrates 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.
• 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.
• Density of comments - illustrates how well source code is accompanied with commentaries. Density is calculated as ratio of commentaries to the total source code produced by the developer. Measured on the scale from 0 to 1.
• Complexity - a McCabe's cyclomatic complexity of the average non commenting code statement produced by the developer.

Developer Know-How Trend

Know-how chart illustrates trends in the developer's know-how throughout the project. Total know-how is divided into shared and unique. The latter 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/her unique know-how. On the opposite, shared know-how measures only knowledge that is shared with other team members. The chart area is the total know-how of the developer in the project.

Developer Complexity Trend

Complexity chart illustrates relation between complexity of average source code statement produced by the developer and density of commentaries. Typically, increase of complexity should result in increase of density of commentaries.

Developer Contribution Size

Contribution size chart illustrates total contribution made by the developer throughout the project and its relation to the amount of source code commentaries written by this developer.

Alumni Report

Alumni report provides information about developers who has left the team during the project. It helps to identify the critical knowledge that has been lost due to the staff attrition.

Unique Know-How Distribution

Illustration of the unique know-how distribution between active team members and alumnis (ex-members). In context of this chart shared know-how is a know-how possessed by both active team and alumnis.

Combined Alumni Know-How Trend

Trends of know-how possessed by all alumnis. Total know-how is divided into shared and unique. The latter measures only knowledge that is not shared with active team members (i.e. only ex-members posses this knowledge). Increase in the unique know-how is often a bad sign because it indicates loss of project expertise and knowledge.

Components with Alumni Know-How

Lists components of the software where alumnis posses unique know-how. Components are sorted in descending order according to the know-how score. Component size estimation indicates relation between component size and size of the whole software.

Know-How Holders

Illustration of know-how distribution between all alumnis. Each team ex-member is characterized using his unique and shared know-how indicators and the list of active team members with whom alumni shares his know-how.