Name

Points

Synopsis

Purpose
Measure the overall productivity of each coder on assigned tasks.
Formula
Points = Sum (Complexity for all completed tasks)

Example

Coder A completes the following assigned tasks in two development iterations:

Iteration 1: Task 1 with Complexity 3
Iteration 1: Task 2 with Complexity 2
Iteration 1: Task 3 with Complexity 4
Iteration 2: Task 4 with Complexity 1
Iteration 2: Task 5 with Complexity 4
Iteration 2: Task 6 with Complexity 2
Iteration 2: Task 7 with Complexity 1

For Iterations 1 and 2, calculate Points as the sum of the Complexity for all completed tasks:

Points Iteration 1 = (3 + 2 + 4) = 9
Points Iteration 2 = (1 + 4 + 2 + 1) = 8

Having calculated the points per iteration, you can then calculate Total Points, or Average Points per Iteration:

Total Points = 9 + 8 = 17
Average Points = (9 + 8) / 2 = 8.5

Notes

This is the basic metric for the amount of work coders are doing on assigned tasks. Each task is weighted by complexity, according to whatever consistent complexity-rating scale you choose (such as a simple scale of 1 to 4). The sum of complexity provides the number of “Points” that corresponds to the relative amount of work done. This, of course, says nothing about the accuracy or quality of the work (which will be indicated by other metrics).

I suggest measuring points per development iteration (such as per sprint if you are using Agile methodology) or per a regular amount of time. Measured periods should probably be at least a week but usually not more than ...

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.