Measuring software quality assurance team performance

We know that performance of developers is measured based on number of defects detected in developed.  But how to measuring software quality assurance team performance. Learn more here

  • No defects should be injected into subsequent phases:Here injecting means putting defects because of making mistakes while doing work. In Quality Assurance context injecting defects means missing defects to find while testing. This also known as defect injection.


a) In Stage 1 testing tester finds 5 defects. These defects are fixed and retested in stage 1. Now the code is promoted to stage 2 for clean run expecting no defects in stage 2.

b) But the tester finds brand new defects say 3 in stage 2 which supposed to be finding in stage 1, so the tester injected 2 defects into stage 2 due to not performing well in stage 1 testing.

  • Zero rejection defects:
    Rejected defects indicates that the defects created for developer investigation is not invalid i.e due to lack of knowledge on application functionality tester has created incorrect test cases which caused to create invalid defects. Also, these invalid defects caused developers to waste time on investigation.
  • No QA Effort Variance:
    It is impossible to get 0% effort variance i.e Actual effort will not be equal to planned effort. Acceptable effort variance will depend upon organization standards. For example, acceptable effort variance for an organization is + or – 20%, so if effort variance is beyond + or – 20% then it will be considered as effort variance. Again, the management should conduct root cause analysis to conclude if effort variance is due to quality assurance performance issues.

Leave a Reply

Your email address will not be published.