Enforce The Quality Bar Example 1
1. I did 30 of quality enforcements (20 latest tickets and 10 past PCA/Customer rejections) and it took me a total of 8 hours. 70% of the units passed the current IQB and 65% of the units passed the current External QB1. With my proposed IQB, only 40% of the units passed, which translates to a 90% 2 pass rate on the EQB. Table with 20 units analyzed for quality (link). Table with analysis of 10 EQB fails (link).
2. The team’s current quality bar has been revamped by the SEM 1.5 weeks after I started working with this team and now consists of a 43 point checklist (which includes >500 Java and >300 C# CRN Severe, Red, and Yellow code quality findings) and it is not good enough.
3. I recommend making these changes to the quality bar:
Define a CC Output Specification that will be the basis for an agreed upon “base” EQB with the customer (PCA) and match it in the IQB checklist. This will solve the issue of a moving target where different PCAs reject for previously undisclosed reasons. Can eliminate ~25% of rejections or 0.82% improvement to FTAR. In the sample eliminates 1 issue (5% improvement).
Add a project-specific Addendum provided by the PCA with a limited set of items specific for a project that-+ must be followed (such as using a specific language version when refactoring, etc). Note: Does not include coding or code quality standards which should follow ESW guidelines and the PCAs must be subject to them. Can eliminate ~31% of rejections or 1.02% improvement to FTAR. In the sample eliminates 2 issues (10% improvement).
Require a minimum 80% method-level UT coverage for code released to the PCA in the Internal Quality Bar and listed in the CC Output Specification, and discuss and agree on 80% coverage in the Input Quality Bar from the HUT team. That means if the refactoring process introduces new methods, the IC has to create UTs for it. Can eliminate ~13% of rejections or 0.41% improvement to FTAR. In the sample eliminates 2 issues (10% improvement).
1)This sample displayed a very high rate of Customer rejections.
2) Two FTAR failures were already in the IQB and can only be resolved through better process rather than IQB additions (see 1 Idea slide).
Last updated
