Productivity of The Software Quality Assurance Team

Productivity of The Software Quality Assurance Team

Software Quality Assurance is an important part of the software development process. One of the factors for delivering quality products is the QA team productivity. This is the ability to quickly find and filter out problems in software, before the end-user gets a hand on it.
Here are some metrics to assess the level of productivity:

#1. Detailed Test Cases. Includes test cases coverage and details. Test cases are based on technical and business requirements. The more details we have, the more possible bugs we prevent. Be careful not to spend too much time on writing cases for trivial things, which on the other hand, sometimes might be forgotten…

#2. Bug Rate. This is the ratio of executed test cases vs number of failed test cases. For example we have 100 cases and 8 failed: 100/8 = 12.5% bug rate.

#3. False positive and false negative rates. The number of false positives/negatives found. Such cases could take a lot of dev team’s time.

  • False positive: marked as failed if it should have passed/ the function tested works properly.
  • False negative – the test passes, but in reality it should have failed. A bug has not been caught. This is the more dangerous one.

#4. Bug documentation. Deals with how well a bug is documented. The more details and proper steps to reproduce, the easier for the devs to understand and fix a bug.

#5. Production/live bug rate – The number of issues after the software release. This could be disruptive to the image and credibility of the company.

#6. Severity of post production bugs. How severe impact a bug has over the product. Some bugs are not that important, but others may cause damage and losses for the client.

#7. Support tickets opened. Total number of calls and tickets to customer support due to bugs reported by customers or end users.