KPIs for a QA Team

This post is somewhat less than lengthy, but I figure this will be of some use regardless.  A while back I was doing KPI discussions for various groups, and got distracted.  Here’s what I measure for QA personnel:

  • Bugs that escape into production:  anything that gets out the door and into a production piece of software or site.  This metric is a direct measure of how good QA staffers are at catching bugs, how good are their test cases, etc.  Also, have bugs prioritized in this, so measuring them by severity will be useful.  If you go over this article –– particularly the section that describes prioritization, that should give you an idea what I’m looking for.
    • Collection of these can come straight out of Jira or other bug-tracking software (issue=bug, create date after UAT start), the QA TL can compile their individual team reports weekly for you and then you can combine those to send a full team report on to me, or you can pull the whole thing together if that’s more convenient.
  • % of bugs caught in-house as a ratio against % of bugs caught outside.  This is a variant of the above, gives us a measure of how much is actually being caught by the team as opposed to a raw count of escapees.
    • Total bugs is a straight pull from your tracking tool, then assemble the ratio based on before and after UAT or launch date
  • Time taken to complete the performance of a test of a feature, or smoke-test, or regression.  Test Velocity is a direct measure of member’s/team’s ability to accomplish their primary mission.
    • Each feature will have time booked against it, TLs can build an excel sheet on these and you can get a baseline average over a month or two which you can measure each individual’s average against
  • Time taken to write a test case of a feature.  As with execution, analysis and assembly of a TC measures their ability to produce one of your key work products.
    • As above, everyone’s booking time against particular features with work descriptions – your TLs can build charts for their teams and you can compile them together.


This entry was posted in Business, Work. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.