Updqate metrics

content/Metrics/_index.md

@@ -6,17 +6,25 @@ weight: 2
 
 > **The most important part of any transformation is measuring the productivity increase.** 
 
-### Lines of code per developer
+### Lines of code per Coder
 
- We need to ensure our coders are focused on the feature 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 coder may try to assume the role of Unit Tester. That wastes time. Therefore, we need to measure the lines of code produced by each coder.
+ We need to ensure our Coders are focused on the feature 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 Coder may try to assume the role of Unit Tester. That wastes time. Therefore, we need to measure the lines of code produced by each Coder.
 
 ### Number of code review comments per convoy
 
-Code review is important to make sure code is formatted correctly. We measure the number of review comments to make sure each coder is being critical enough of the work of other coders. 
+Code review is important to make sure code is formatted correctly. We measure the number of review comments to make sure each Coder is being critical enough of the work of other Coders. 
 
-### Tasks Delivered per Developer
+### Tasks delivered per Coder
 
-For each developer, the number of tasks they complete during Convoy. By tracking the number of features each coder completes, more can be shipped in each Convoy. Volume is important. Let's turn it up to 11!
+For each Coder, the number of tasks they complete during Convoy. By tracking the number of features each Coder completes, more can be shipped in each Convoy. Volume is important. Let's turn it up to 11!
+
+### Defects created by Coder
+
+For each Coder, we should track the number of defects they create and use this information to inform the Tribunal. We must "[build quality in](../principles/#build-quality-in)" by eliminating the source of defects.
+
+### Defects detected by Testers
+
+For each Tester, we should track the number of defects they detect and use this information to inform the Tribunal. We must "[build quality in](../principles/#build-quality-in)" by eliminating Testers that cannot find defects.
 
 ### SADMF Maturity Score
 

content/Organization/_index.md

@@ -8,8 +8,8 @@ weight: 2
 
 ### Source Management Team
 
-To improve coder productivity by reducing the work required for integrating changes, we introduce the Source Management Team. The SMT is responsbile for accepting the complete [feature branches](../practices/#fractal-based-development) from each coder and merging the changes into the Conflict Resolution branch. They will then resolve all conflicts for the coders before alerting the Quality Control team that the Convoy is ready for testing.
+To improve Coder productivity by reducing the work required for integrating changes, we introduce the Source Management Team. The SMT is responsbile for accepting the complete [feature branches](../practices/#fractal-based-development) from each Coder and merging the changes into the Conflict Resolution branch. They will then resolve all conflicts for the Coders before alerting the Quality Control team that the Convoy is ready for testing.
 
 ### Quality Authority
 
-Verifying quality is a specialist field that no coder is qualified to perform. In addition, performing testing impedes the ability for the coder to do their job, write code. The Quality Authority team is the final arbiter of what the requirements mean and will create, maintain, and manually execute tests scripts based on their understanding of the requirements. The end-user uses the system manually, so that is the only TRUE way to test it!
+Verifying quality is a specialist field that no Coder is qualified to perform. In addition, performing testing impedes the ability for the Coder to do their job, write code. The Quality Authority team is the final arbiter of what the requirements mean and will create, maintain, and manually execute tests scripts based on their understanding of the requirements. The end-user uses the system manually, so that is the only TRUE way to test it!

content/Principles/_index.md

@@ -18,11 +18,11 @@ Coaching employees is an important daily practice to ensure they know we are tra
 
 ### Everyone is responsible
 
-Each person is responsible for their individual work and should be rewarded for the work they do. If a feature is successfully delivered, we should identify the coder who made the most changes and give them a bonus. It would be unfair to reward the whole team based on the excellence of an individual.
+Each person is responsible for their individual work and should be rewarded for the work they do. If a feature is successfully delivered, we should identify the Coder who made the most changes and give them a bonus. It would be unfair to reward the whole team based on the excellence of an individual.
 
 ### Psychological safety
 
-We know the [Tribunal](../release-convoy/#tribunal) can be a stressful time when we need to remove coders. We will use automated systems for "Human Resources as a Service" to automatically help coders find new opportunities outside our company so we can avoid confrontation.
+We know the [Tribunal](../release-convoy/#tribunal) can be a stressful time when we need to remove Coders. We will use automated systems for "Human Resources as a Service" to automatically help Coders find new opportunities outside our company so we can avoid confrontation.
 
 ### Systems Thinking
 

content/Release Convoy/_index.md

@@ -28,7 +28,7 @@ Meeting of the Feature Captains to plan the date when the Release Convoy™
 
 #### Press Gang
 
-In the Press Gang step, the Feature Captain will choose between 2 and 20 people from the coding pool to "self-organize" around delivering the next feature. This ensures each coder is given the opportunity to work on new and interesting things and that all coders are fully utilized.
+In the Press Gang step, the Feature Captain will choose between 2 and 20 people from the coding pool to "self-organize" around delivering the next feature. This ensures each Coder is given the opportunity to work on new and interesting things and that all Coders are fully utilized.
 
 #### Post Standup Standup
 
@@ -44,11 +44,11 @@ To effectively scale communication, we use the Scrum of Scrum of Scrums. First t
 
 #### Manufacturing
 
-The group of coders assigned to each feature will implement the requirements they are given as rapidly as possible using the industry best practice, *[Continuous Isolation](https://continuousisolation.com)*. This ensures it can be tested and delivered on the Convoy it is planned for. Once the feature is coded, the coders can return to the coding pool to await their next adventure!.
+The group of Coders assigned to each feature will implement the requirements they are given as rapidly as possible using the industry best practice, *[Continuous Isolation](https://continuousisolation.com)*. This ensures it can be tested and delivered on the Convoy it is planned for. Once the feature is coded, the Coders can return to the coding pool to await their next adventure!.
 
 #### Testing
 
-The to keep the coders productive, we need them to focus only on coding. For unit testing, the Feature Captain will assign the complete feature to the Unit Testing Team to ensure 100% test coverage.
+The to keep the Coders productive, we need them to focus only on coding. For unit testing, the Feature Captain will assign the complete feature to the Unit Testing Team to ensure 100% test coverage.
 
 #### System Integration Testing