So you read my Edible versions post and want to get the good stuff on how to make it happen in your organization. Well, to be honest, its not that difficult once all the parties sit together, talk about their expectations and design the protocols between the groups. See my earlier post for some general pointers.Having said that - Maybe I CAN provide some tips that I saw working in the past:Ensure all content in a delivery is tracked as [...]
How do you know your QA effort is being effective ?Based on the different stakeholders which require input from the QA a typical answer might be that Product quality is high when released to customers.Assuming that is indeed more or less what someone expects (I'd say effective QA needs to answer to some other requirements as well) how does one go about checking whether the product quality is indeed high?Those who reached a fairly intermediate level of QA understanding would [...]
There are a couple of alternatives for managing severity and priority in the Issue Tracker.Although there are many resources out there on this subject (see http://del.icio.us/yyeret/priority_severity) I’ll try to consolidate them and provide my 2c on the matter, as I think its an important subject.Single-field PriorityFirst, seemingly simpler alternative, is Single-field priority – representing Customer ImpactThe idea here is to only have a single priority/severity field. The reporter assigns it according to his understanding of the customer impact (severity, likelihood, [...]