No priority or severity assigned

Incident numbering is manual rather than automated

No mentioning of reproduceability

No classification on type of incident

Test planning, test case preparation and test execution for each of the four iterations

Work should be explicitly allocated to test completion, test management, installation and to training on using the system

Activities to deploy the system in the user environment

Regression testing in the second, third and fourth iterations

Development activities for unit and integration testing

Reviews on requirements documentation

Defining test environment requirements for system testing

A test strategy should address identified generic product risks and present a process for mitigating those risks in line with the testing policy.

A test strategy identifies the specific product for a project risk and defines the approach for the test project.

A test strategy is derived from the test policy and describes the way risk assessments are performed in projects.

A test strategy is the result of a project risk analysis and defines the approach and resources for testing.