Codermetrics

Name

Saves

Synopsis

Purpose

Measure how often a coder helps fix urgent production issues.

Formula

Saves = Number of Product Issues with the highest Severity that a coder helps fix

Example

The following production issues are found and are rated on a severity scale from 1 to 4:

Issue 1 with Severity 2

Issue 2 with Severity 3

Issue 3 with Severity 4

Issue 4 with Severity 1

Issue 5 with Severity 4

Issue 6 with Severity 3

For the purpose of calculating Saves, the relevant production issues are those with the highest severity. In this example, that would be Issues 3 and 5 from the list above. For these issues, Coder A is assigned the following tasks that are completed over two development iterations:

Iteration 1: Task 1 with Complexity 3 (related to Issue 3)

Iteration 1: Task 2 with Complexity 2 (related to Issue 3)

Iteration 2: Task 3 with Complexity 2 (related to Issue 3)

Iteration 2: Task 4 with Complexity 4 (related to Issue 5)

Iteration 2: Task 5 with Complexity 1 (related to Issue 5)

To calculate Saves per iteration, you sum the number of the highest severity issues that the coder helped fix, tallying each when the final task related to a production issue is completed:

Saves Iteration 1 = 0 (none of the issues is fully resolved)

Saves Iteration 2 = 2 (all tasks for issues 3 and 5 complete)

Then you can use the iteration Saves to calculate Total or Average for all iterations:

Total Saves = (0 + 2) = 2

Average Saves = (0 + 2) / 2 = 1

Notes

In calculating Saves, the size of the population affected and the complexity ...