Got an interesting mail so thought Id share it with eone.
Developers always have an issue with QA classifying bugs – The general trend has been to classify an issue based on how much of functionality a particular bug blocks/prevents the user from accessing. But consider this new approach – Though it made us go nuts initially with almost all minor bugs suddenly getting promoted to blockers, I feel it’s a very interesting approach – Let me know what you think.
Trivial – Not likely to Business/Power user bump into it, because it requires some prior and rather technical configuration or high level technical background. So in general until now, if a particular key combination(keyboard short cut) crashed the app, QA would consider it a blocker. But with this approach the QA would need to look at what is the probability of someone using that key combination, and if it is rare it would only be a trivial issue!
Minor – Not likely to Business/Power user bump into it, because it requires medium technical background.
Major – Business/Power user with little technical background might bump into it after several hours of interacting with the tool.
Critical – Business/Power user with no technical background at all, might bump into it after a few hours session with the tool.
Blocker – Very likely that Business/Power user with no technical background at all, will bump into it in the first couple of hours with the tool. So, until now you might consider a ‘spelling mistake’ on the front page to be a minor issue, but with this approach it becomes a blocker!!!!
A complete turn around – but for the marketing team it means they can sell the product better! What do you think?
Blogged with Flock