Management via metrics is the most effective way to cause impact!
Code Engineers must be focused on their features for the next convoy. The fleet won’t wait! We also need to ensure we have balanced metrics to prevent a perverse incentive when we track who created defects. If we only track defects, the Code Engineer may try to assume the role of Unit Tester . That wastes time. Therefore, we need to measure the lines of code produced by each Code Engineer to ensure productivity.
Code review is important to ensure code is formatted correctly. We measure the number of review comments to verify each Code Engineer is being critical enough of the work of others.
For each Code Engineer , the number of tasks they complete during Convoy. By tracking the number of features each Code Engineer completes, more can be shipped in each Convoy. Volume is important. Let’s turn it up to 11!
The precise execution of the SAD Delivery Lifecycle is critical to the success of SADMF. Without “excellent” maturity scores, your customers will have no confidence you used SADMF to deliver!
The percentage of features delivered in the Convoy compared to what was committed to 8 quarters ago.
The percentage of the organization that has received a SAD™ certification .