Business Driven Test Management (BDTM) is the new way how to define a test strategy in TMap. Testing of software should be based on the business risks for the organisation in using that software. In practice, the test manager often takes the steps to go from risks to test coverage in an intuitive way. In BDTM, the steps to define a testing strategy are made explicit.
This gives all parties involved better insight and provides a sound basis for negotiating testing depth. It aims at giving the business (customer) or project manager control over the test process, while the test manager remains in the driving seat. Leading terms in BDTM are: time, cost, risk and benefits. Especially this last point is not often addressed in testing. The test process is followed from start (planning) to end (reporting), discussing the specific aspects of BDTM. Discussing risks and testing in the above way proves in practice to be real eye-openers for all parties concerned. This also enables negotiating about testing depth/coverage by letting the customer choose what should be tested how thoroughly.
The stepwise defining of the test strategy can be used for any test level and also for an overall strategy, including and co-ordinating all test levels and even inspections.
NOTE: The BDTM paper below has not yet been reviewed for correct use of the English language.
|
