Workflow Detail: Define Evaluation Mission
| The purpose of this workflow detail is to identify the appropriate focus of the test effort for the iteration, and to gain agreement with stakeholders on the corresponding goals that will direct the test effort. | |
| Topics - Description - Related Information - Timing - Optionality - How to Staff - Work Guidelines |
Description
For each iteration, this work is focused mainly on:
- Identifying the objectives for, and deliverables of, the testing effort
- Identifying a good resource utilization strategy
- Defining the appropriate scope and boundary for the test effort
- Outlining the approach that will be used
- Defining how progress will be monitored and assessed.
Related Information
This section provides links to additional information related to this workflow detail.
- Concept: Evaluating Quality
- Concept: Key Measures of Test
- Concept: Measuring Quality
- Concept: Product Quality
- Concept: Test Strategy
- Concept: The Lifecycle of Testing
- Whitepaper: Traceability Strategies for Managing Requirements with Use Cases
Timing
Typically addressed toward the beginning of each iteration before other test-related work commences.
Optionality
Should be performed in each iteration that will result in an executable release.
How to Staff
Although most of the roles involved in the Test discipline play a part in performing this work, the effort is primarily centered around the Test Manager and Test Analyst roles. The most important skills required for this work include negotiation, elicitation, strategy and planning.
While most of the resource for this work will be expended in Construction, significant resources will need to be allocated to this work from Inception to Transition. As a relative indication of test resource use for this workflow detail by phase, typical percentages are: Inception - 50%, Elaboration - 25%, Construction
- 10% and Transition - 10%.
Work Guidelines
Note that this work is performed in each iteration. We recommend that you don’t spend a lot of time on the detailed planning of testing tasks too far in advance of the iteration in which they are performed-as a general rule, don’t plan detailed testing work further than one iteration ahead.
The main value in performing this work is to think through the various concerns and issues that will impact testing over the course of the iteration, and consider the appropriate actions you should take. As a general rule, don’t spend excessive amounts of time on the presentation of the documentation for these aspects of the test effort.
See the Related Information section for additional guidance that will help you in performing this work.