It's this time of the year again, we're looking at Key Performance Indicators to measure the testing and QA team against. This time we better come up with something before someone else does.
Judging tester performance by numbers of bugs logged is out for all the obvious reasons.
Some ideas could be
- % of requirements covered by testing
- Number of information requests from developers for logged bugs (not enough information in the logged bug - encourages testers to go the extra mile)
- Rework of test scripts (Are test scripts right from the start or do they have to be updated all the time)
I know all of the above are somewhat flawed, what's your take on it? Is there anything that you would feel happy being measured against?
I think numbers can be helpful in the big picture, but they are not always applicable. Conditions or special projects tend to always throw these off.
I "feel happy" when measurement is based on:
1. Peer feedback (PM, Developer, other QA). The classic "Start, Stop, Keep" works well for this feedback.
2. Acheivment of prior set goals.
You already seem to realise that it's a difficult task and runs into the problem that it can either be gamed or is unfair as 'it depends' on circumstances not always under the testers control
Sticky Minds article from Elfriede Dustin here along with a good discussion aferwards