RE: How can the efficiency of the Tester be mapped? Is...
Two methods I have seen in action: 1. Quota: Some companies mandate that a Tester must find X number of defects a month and write X number of testcases. *This results in duplicate defects and an unwieldy amount of testcases which bog down the testing process.
2. Accountability: Assign areas or processes/functionality of the program to each of the QA's and monitor the usability and maturity of the product. Set goals for Usability and Maturity to become better. If a QA misses issues or does not run properly written testcases the product would suffer. *This is by far the best method. It encourages accuracy and efficiency.
RE: How can the efficiency of the Tester be mapped? Is there any process flow or matrix for this?
"Efficiency of tester" comes under arts also. As one friend described 2 methods above both are fine but another major source to map tester efficiency is "Analysis of your Bug Database". Develop matrices to based on user How many bugs reported by Mr X? What are statistics based on the severity of bugs reported by Mr. X i.e. How many Blockers how many Serios How many Major and minor etc. How many bugs reorted by X are marked invalid? How many design issues reported by X? so on so far based on process you are following.
Where there is question of intangible parameters we can analyse like: How hardwork X is? Extra time/effort put by X? How creative X is in testing? Is he introduced any new domain of testing?
RE: How can the efficiency of the Tester be mapped? Is there any process flow or matrix for this?
One more I would like to add like How many bugs Mr X has missed and those bugs are found in UAT. and How many bugs missed by Mr X in UAT and those are found in Production....
