Thursday 9 May 2013

Tester KPI

Confused over how to rate yourself as tester ? what are the key indicators for functional , non functional tester.

 A good coding skills, documenting skills, interfacing skills, attention to detail, more number of  bugs , analyzing bugs and proving resolution , generating  good scenarios , finding bugs in quality cycle earlier through review are some of the things one should look for before defining the KPI.

Or are there bunch of another things like number of  number test cases or effective number of test cases  number of requirement works against , effective reporting . The quantifiable metrics may or may not be the best approach to define the KPI.

The are more adjective applied to different tasks and how to evaluate these. Say number of test cases and effective number of test case . How to say which metrics is good KPI for the tester. How do you evaluate these metrics. One approach would be to review the same but then who review all the test cases ; another way would be reverse engineering through bug leakage  then again it takes time and probably you are too late .

Through i am not against the quantitative metrics for KPI  but i think these same can evaluate your good tester as bad and vice versa. So just have caution before you proceed with metrics

No comments:

Post a Comment