Name
Turnovers
Synopsis
- Purpose
Measure the complexity of assigned tasks that a coder fails to complete. - Formula
Turnovers = Sum (Complexity for all completed Tasks)
Example
Coder A fails to complete the following tasks in three development iterations:
| Iteration 1: Task 1 with Complexity 3 |
| Iteration 2: Task 2 with Complexity 4 |
| Iteration 3: Task 3 with Complexity 3 |
Calculate the Total and Average Turnovers as follows:
| Total Turnovers = (3 + 4 + 3) = 10 |
| Average Turnovers = (3 + 4 + 3) / 3 = 3.3 |
Notes
The Turnovers metric is equivalent to “Points for Incomplete Tasks.” This, along with Errors, is one of the basic metrics covering coder “mistakes.” Turnovers are weighted by the Complexity of each incomplete Task, assuming that it is a “bigger” mistake to leave a more complex task incomplete.
For most developers, the number of Turnovers will be small, approaching, or at, zero. It’s just the nature of how we manage software projects and software development teams that most developers will not give up on a task before it’s complete, and most managers will not reassign tasks. Tasks where a coder receives help do not count as Turnovers. Tasks that are reassigned from one coder to another for scheduling efficiency, simply because the original coder was too busy, also don’t count. Turnovers refer specifically to tasks that a coder began and was expected to finish but couldn’t due to technical struggles or other encountered problems.
In certain cases, such as when dealing with very junior coders or interns, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access