How do you measure quality assurance and quality of products in your teams? What metrics do you use? What tools do you use?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
closed as not a real question by corsiKa♦, Robert Cartaino♦ May 4 '11 at 15:13
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.
There are no "best" practices in my opinion. As others on the internet stated before, there might be "good" or "good enough" practices.
You have to see it in context. One good practice which fits perfectly for your company, product, people, etc.. (~context), might be TOTALLY wrong in my company, product, people, etc. :-)
Also on the note of "metrics". This can be a dangerous thing as well. Often you get, what you measure.
If I would be evaluated/paid by the amount of bugs, you can bet, that I would find dozens every day (or what ever the needed amount is).
If this would be "real" bugs or not.. wouldn't matter much for me (if my pay depends on it).
Also for developers: If you measure them by lines of code, you can bet you get dozens of lines, even when the function could be neatly fit in one line.