Name
Teamwork
Synopsis
- Purpose
Establish a relative rating for team-oriented contributions. - Formula
Teamwork = Assists + Saves + Range - Turnovers
Example
The individual coders on a software team are measured to have the following Skill Metric values for a software release:
Coder A: Assists 62, Saves 7, Range 2, Turnovers 22 |
Coder B: Assists 48, Saves 3, Range 6, Turnovers 11 |
Coder C: Assists 91, Saves 0, Range 4, Turnovers 7 |
Coder D: Assists 70, Saves 1, Range 3, Turnovers 0 |
The Teamwork metric for each coder can then be calculated as follows:
Teamwork Coder A = 62 + 7 + 2 - 22 = 49 |
Teamwork Coder B = 48 + 3 + 6 - 11 = 46 |
Teamwork Coder C = 91 + 0 + 4 - 7 = 8 |
Teamwork Coder D = 70 + 1 + 3 - 0 = 74 |
Notes
Summarizing the Skill Metrics that correlate with a variety of ways that coders help and support teammates, the Teamwork metric provides a relative value to identify coders who are strongest in this regard. Coders with a high Teamwork rating can be said to exhibit a higher level of teamwork in the kinds of contributions they make.
Having a low Teamwork rating does not mean a coder is a bad teammate, or even that the coder is lacking in teamwork in any way. That coder may have had other responsibilities that fall outside the elements this metric measures. A coder might take note if they have a lower Teamwork rating than others, but it doesn’t necessarily mean they did anything wrong. In this sense, I suggest you look at this metric (and all other Rating Metrics) as especially useful for identifying ...
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.