August 2011
Intermediate to advanced
264 pages
8h 42m
English
O-Impact
| Provide a single “Offensive Impact” number that summarizes the contributions of a coder in moving projects along. |
| O-Impact = Points + Utility + Assists |
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 |
Coder A is also noted for the following number of Interrupts and Helps during two iterations:
| Iteration 1: 4 Interrupts, 2 Helps |
| Iteration 2: 1 Interrupt, 2 Helps |
The coder’s O-Impact for each iteration is calculated in the following way:
| Points Iteration 1 = (3 + 2 + 4) = 9 |
| Utility Iteration 1 = 3 |
| Assists Iteration 1 = (4 + 2) = 6 |
| O-Impact Iteration 1 = (9 + 3 + 6) = 18 |
| Points Iteration 2 = (1 + 4 + 2 + 1) = 8 |
| Utility Iteration 2 = 4 |
| Assists Iteration 2 = (1 + 2) = 3 |
| O-Impact Iteration 2 = (8 + 4 + 3) = 15 |
Using the calculated O-Impact per iteration, you can calculate the coder’s Total or Average:
| Total O-Impact = (18 + 15) = 33 |
| Average O-Impact = (18 + 15) / 2 = 16.5 |
Sometimes, when looking for trends and patterns, it is easier to look at summary metrics, even if these are merely combinations of other more detailed metrics. In baseball, there are statistics for all the different types of hits, and then there are statistics like Total Bases that summarize different types ...
Read now
Unlock full access