Listed in Table 4-1 are the input data elements that will be used in the Skill Metrics. These data elements were discussed in more detail in the previous chapter. It is assumed that you will measure each of these in some regular time interval. For example you might measure and record this data weekly, or if you have two-week development iterations, you might measure biweekly.
Table 4-1. Input data for Skill Metrics
| Element Name | Description |
|---|---|
| Tasks | Assigned tasks completed by each coder |
| Complexity | Complexity rating of each assigned task |
| Incompletes | Assigned tasks that coder failed to complete |
| Product Issues | Production bugs by product area |
| Severity | Severity rating of each bug, possibly boosted for regression bugs |
| Population Affected | Percent of customers (estimated or known) affected by each bug |
| Areas Worked | Number of product areas worked on by each coder |
| Issues Fixed | Production issues fixed by each coder (as part of assigned tasks) |
| Interrupts | Number of times coder is significantly “interrupted” on assigned activities to respond to requests |
| Helps | Number of times coder proactively helps others in significant ways |
| Pluses | Number of times coder demonstrated significant initiative or innovation |
Get Codermetrics now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
