Enforce the Quality Bar Example 2

1. I did 30arrow-up-right quality enforcements and it took me a total of 7 hours. 21.3%arrow-up-right of the units passed the current External QB. Currently the team does not have an Internal Quality Bar. With my proposed IQBarrow-up-right (implementation planarrow-up-right), only 3.6%arrow-up-right of the units passed. Overall my proposed IQB would improve EQB FTAR by 8.53% to 100%arrow-up-right. Table with 30 units analyzed for quality (linkarrow-up-right).

2. The team’s coding standards are documentedarrow-up-right, but are not enforced and do not constitute an actual IQB. I recommend creating and enforcing an Internal Quality Bararrow-up-right.

3. I recommend making these changes to the quality bar:

  1. Add 'Static code analysis tools detect no issues in the pull request (SonarLintarrow-up-right)' to the internal quality bar. This would eliminate 12 EQB failures in T8W. There would be a 4.21% increase in FTARarrow-up-right.

  2. Add 'The pull request compiles and all tests pass' to the internal quality bar. 6 tickets in T8Warrow-up-right were affected by build issues. As a result there will be a 3.85% increase in FTARarrow-up-right.

  3. Add 'The pull request provides a 100% method-level coverage of non-autogenerated classes' to the quality bar. PCAs complained about inadequate test coverage in 6 tickets in the last 8 weeksarrow-up-right. Preventing those issues will yield 1.08% improvement in FTARarrow-up-right.

Last updated

Was this helpful?