Context
This activity relates to all test and evaluation levels involved in the master test plan, as already described in Plan (MTP). The testing may relate to new development, maintenance, migration, a
package implementation, or a mix of these elements. The development approach may be waterfall, iterative, agile or a
mix. Depending on the agreements reached, the test manager may have a managing, coordinating or simply observing role
in relation to a test level.
Preconditions
This activity starts after the master test plan is created or once one or more of the relevant test and
evaluation levels have started.
Method of operation
The test manager and administrator(s) execute the activities assigned to them in the master test plan. They
manage the test process, infrastructure and test products, partly on the basis of the data supplied by the test levels.
Based on this data, the test manager analyses possible trends. He also ensures that he is well informed of the
developments beyond testing, such as delays in development, upcoming big change proposals and project adjustments. If
necessary, he proposes specific control measures to the client.
Information is the main product of testing. To this end, the test manager creates different kinds of reports for the
various target groups, taking account of the BDTM aspects of Result, Risks, Time and Costs.
Roles/responsibilities
The test manager or overall test coordinator is the role primarily responsible for (the coordination of) the
management of the total test process.
Furthermore, certain roles may be created at the overall test level for management and support, both for the overall
level and for the separate test levels.
Activities
Managing the total test process consists of the following activities:
-
Management
-
Monitoring
-
Reporting
-
Adjusting.
The diagram below shows the order of and dependencies between the various activities, with the arrow demonstrating that
the activities are emphatically iterative:
Figure 1: Control of the total test process
|
