This post is about the opportunities given by a test strategy on the evaluation process. The use of an evaluation strategy.

Finding defects in an early stage of the product is the cheapest manner of increasing the quality of a product. Everybody in ‘quality land’ knows this! The way to do this is by using evaluations, like reviews. But this isn’t done by many. Why?

Well first of all it is expensive to do. And you don’t get much in return in a project. A projectleader will only see it at the end of the project, when there is less testing done. It also is difficult to do right. When do you use which evaluation technique on which product? The easiest way to do this is by using an evaluation strategy. This is much like a test strategy. A test strategy is created by using risk classes, test levels and combine these with test design techniques. The result is a strategy of testing the high risk pieces of software most thorough. Because “No risk, no test!”

How can this be done when evaluating intermediairy products? The same to be exact. A QA Manager should do a risk analysis for the product of the project. The risk analysis should include the evaluation goals of the project, the delivered products and the risks of these combines. Now you have an risk analysis for the intermediairy products. So you get a list like underneath.

When combining these risk classes and products with evaluation techniques you get a clear view of the importance of the risks. A high risk product should be thoroughly reviewed. See the next table.

Now, how do you get the effectiveness in the evaluation strategy? The answer is: by using reading techniques! With a reading technique you get insight in the document without overdoing the review or inspection. For example. The risk of documenttype Funtional Design is ‘A’ (the highest) and you evaluate it with a (Fagan) inspection the process is quite expensive. When using PBR (Perspective Bases Reading) reviewers only look at a docuement from their perspective. Thus, getting better results in finding defects in less time.

When using all these options into the evaluation strategy you get this result.

An other benefit is that with using a evaluation strategy, like a test strategy, you always stick by the business case while doing quality assurance in your project. This generates the best results and at the end a cheaper project with less risks to fall behind on planning…