The levels for Degree of involvement are typified as follows:
Please find the checkpoints below.
Controlled | |||||||||||
1. The test assignment, scope and approach are negotiated early with the principal stakeholder as one of the first test activities. 2. Test activities are started early, timely before test execution, with the goal of keeping the test activities of the project’s critical path. 3. A tester is involved in project planning: dependencies between the test process and other processes are taken into account. 4. A tester is involved in the analysis and mitigation of overall project risks. |
|||||||||||
Efficient | |||||||||||
1. Testers contribute to impact and risk analysis of change requests and changes to the test basis. 2. Testers contribute to the impact analysis of defects. 3. Testers are actively involved in optimizing the test basis (more than a testability review), in which the object under test is described. |
|||||||||||
Optimizing | |||||||||||
1. The test team is involved in the evaluation of the project. The lessons learned from the test process are valued and used for (the set up of) future projects. 2. The test team has an undisputed part in all relevant development activities, being accepted and valued. |
(Source: “TPI Next, Business Driven Test Process Improvement” ISBN 9072194977)