Explore and then select a limited number of effective test techniques (not more than 10) that:

Have been proven in practice

Appear to apply to your context

Can be easily understood by programmers, designers, and testers.

Establish a training program to instruct programmers and quality assurance personnel in the use, limitations, objectives, and most likely areas of application of the various test techniques.

Establish non-binding guidelines for the use of different test techniques in the circumstances to which they best apply - e.g., functional/structural, unit/ system level, etc.

Review test plans for correspondence to test method guidelines and investigate seeing deviations. Don't be dogmatic about using the ":right" test design method.

Monitor the effectiveness of the methods you use with respect to:

The number of bugs caught

The severity and publicness of those bugs

The level (unit to system) at which the bug was caught

The application context

Tune your methods in accordance to the data gathered and emphasize the methods that have the best payoff. Keep in mind the quality assurance uncertainty principle, that application of these methods will change the data.

Listen to the programmers and designers for test method suggestions and keep on top of the test literature - be ready willing and able to adopt and implement any method that works