Development activities and testing activities should be organized independently. This separation should be as clear as possible.
Depending on the tasks to be executed, staff with social competence is required. Low social competence = somebody gets humiliated. Humiliation will block effective testing and production.
The test managers tasks are: The initial planning of the tests, plus further planning, monitoring and controlling the different test cycles.
The test plan is where the test manager describes and explains the test strategy. The international standard IEEE 829 provides a checklist for format and content
There are a break-even-point between testing costs and the estimated costs of a faulty product. The costs for both issues have to be balanced through priorities.
One of the best metods to prioritize the effort, is by risk assessment. Risk-based testing uses information about identified risk fro planning, specification, preparation and execution of tests. All major elements of the test trategy are determined on the basis of risk, just the same way as risk-based development.
Measurable exit criteria define when testing can be stopped. Without given exit criteria, testing might stop randomly.
The basis for an effecient test process, are formed by incident management and configuration management.
The incident-reports must be collected, systematized and kept throughout the entire project. The relevant parts must be updated to follow the development – just as any agile documents must be updated and changed throughout any development process.
Standards contain specifications and recommendations from peers. Following such standards utilizes the experience of the peers, even if it is neither mandatory or eligible to follow them strictly.
Testing is creativity..