Method of operation

During the test project, the test manager creates various reports. In the master test plan, the chapter “Management” specifies the type and frequency of reporting. Periodical reports are made on the quality of the test object and the progress and quality of the test process. In addition to the periodical reports, the client or other stakeholders may request ad hoc reports. The most common example is the risk report to map the possible consequences of a threat or risk to the test process and propose countermeasures. Furthermore, a sudden request for an additional progress report may be made, e.g. as most up-to-date input for a project board or project management meeting. A release advice and final report are compiled at the end of the test process.

All this information provides the client, project manager and other stakeholders with insight into the degree to which:

• the intended result has been achieved
• the risks during commissioning are known and as small as possible within the framework of the defined preconditions
• this is done within the defined budget and proposed (lead) time.

In other words, these are the BDTM aspects of Result, Risks, Time and Costs. Providing insight means that the report must match the perception of its recipients.

The reports are based on the data as recorded that conforms with Organise The Management (MTP). The data are supplied mainly by the test levels.

The main reports are:

• progress report
• risk report
• release advice
• final report.

These reports are described in detail in Report (AST).

Products

• Reports (progress report, risk report, release advice, final report)
• Experience data
• Cost/benefit analysis.

Techniques

• Checklist “Test process evaluation”
• Metrics

Tools

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