Method of operation

The main and most difficult task of the test manager is monitoring the execution of the master test plan. While described as a very instrumental activity in the section below, this is mainly a communicative activity with employee, stakeholder and expectation management that requires strong social and communication skills.

Generally speaking, the test levels described in the plan must be executed according to a specific time path and in a certain order. The test manager must be able to determine whether it is wise to start testing. Towards the end of test execution, the test manager must be able to answer the question whether it is wise to stop testing.

Practice has shown that deviations from the original plan often occur. Such deviations may have a cause both inside and outside the test process. Examples of the former are that specifying or executing test cases proceeds more slowly than expected (the testers are less productive than expected), or that certain test levels cannot begin testing according to the planning (due to an incorrect assessment beforehand). Examples of the latter are: inadequate quality of the test basis or test object, additional change proposals, or delays in design or development. The test manager must detect such events or trend as early on as possible. He can then take timely measures to correct a negative trend. This is nearly always better, more economical and faster.

The information for the events or trends is supplied from several sides:

• Internally managed data at the overall level
• Data supplied by (reports of) the test levels
• Information from outside the test process supplied by documentation like minutes or memos, but certainly also by spoken consultation, such as project meetings, bilateral consultations, stand-up meetings, etc.

The spoken source of information in particular underlines the importance of good (social) skills and external orientation on the part of the test manager.

On the basis of the data, the test manager analyses possible trends and tries to detect threats (or opportunities) in time. He executes the following steps to this end:

1. Analysing the event, estimating risks and defi ning countermeasures
2. Coordinating with the client and other stakeholders (optional, depending on tolerance)

These steps are described in detail in Monitor (AST). This current task limits itself to explaining certain specific issues for the master test plan.

Products

Proposed control measures.

Tools

• Defect management tool
• Testware management tool
• Workflow tool
• Planning and progress monitoring tool.