Artifact: Measurement Plan
| Defines the measurement goals, the associated metrics, and the primitive metrics to be collected in the project to monitor its progress. | |
| Other Relationships: | Part Of Software Development Plan |
| Role: | Project Manager |
| Optionality/Occurrence: | Optional. Once per development cycle. |
| Templates and Reports: | - Template: Measurement Plan |
| Examples: | - Classics CD.com Measurement Plan |
| UML Representation: | Not applicable. |
| More Information: | - Guideline: Metrics |
| Input to Activities: - Assess Iteration - Compile Software Development Plan - Develop Quality Assurance Plan - Monitor Project Status | Output from Activities: - Define Monitoring & Control Processes - Develop Measurement Plan |
Purpose
The software Measurement Plan specifies what primitive metrics should be collected and what metrics should be computed during the project to monitor progress, relative to a set of specified project goals (see Concepts: Metrics). It is used to collect information on the project as input to the periodic Status Assessment (see Artifact: Status Assessment).
Timing
The Measurement Plan is done once per development cycle, in the Inception phase, as part of the general planning activity, or sometimes as part of the configuration of the process in the Development Case. The Measurement Plan may be revisited like any other section of the Software Development Plan during the course of the project.
Responsibility
The Project Manager is responsible for the integrity of the Measurement Plan, ensuring that:
- the goals are relevant to the project.
- the primitive metrics can all be collected at minimal overhead and, if possible, using tools.
The Measurement Plan is a part of the more general Artifact: Software Development Plan.
Tailoring
The Measurement Plan may physically be part of the Software Development Plan if the metrics program is a simple one.