Appendix VII: Sample Measurement Plan
Abstract
This document contains an example of a standard defining the contents and structure of a Software Measurement Plan for each project of an organization. The term Measurement Plan will be used throughout.
Table of Contents
- Introduction
- Policy
- Responsibility and Authorities
- General Information
- Thematic Outline of Measurement Plan
1 Introduction
This standard provides guidance on the production of a measurement plan for individual software projects.
1.1 Scope
This standard is mandatory for all projects. Assistance in applying it to existing projects will be given by the organization measures coordinator.
2 Policy
It is policy to collect measures to assist in the improvement of
- The accuracy of cost estimates
- Project productivity
- Product quality
- Project monitoring and control
In particular, each project will be responsible for identifying and planning all activities associated with the collection of these measures. The project is responsible for the definition of the project’s objectives for collecting measures, analyzing the measures to provide the required presentation results, and documenting the approach in an internally approved measurement plan. The project is also responsible for capturing the actual measurement information and analysis results. The form of this actual measurement information could be appended to the measurement plan or put in a separate document called a measurement case.
3 Responsibility and Authorities
The project leader/manager shall be responsible for the production of the project measurement plan at the start of the project. Advice and assistance from the organization measures coordinator shall be sought when needed. The measurement plan shall be approved by the project leader/manager (if not the author), product manager, organization measures coordinator, and project quality manager.
4 General Information
4.1 Overview of Project Measures Activities
The collection and use of measures must be defined and planned into a project during the start-up phase. The haphazard collection of measures is more likely to result in the collection of a large amount of inconsistent data that will provide little useful information to the project management team, or for future projects.
The following activities shall be carried out at the start of the project:
- Define the project’s objectives for collecting measures.
- Identify the users of the measures-derived information, as well as any particular requirements they may have.
- Identify the measures to meet these objectives or provide the information. Most, if not all, of these should be defined at the organization level.
- Define the project task structure, for example, work breakdown structure (WBS).
- Define when each measure is to be collected, in terms of the project task structure.
- Define how each measure is to be collected, in terms of preprinted forms/tools, who will collect it, and where/how it will be stored.
- Define how the data will be analyzed to provide the required information, including the specification of any necessary algorithms, and the frequency with which this will be done.
- Define the organization, including the information flow, within the project required to support the measures collection and analyses activities.
- Identify the standards and procedures to be used.
- Define which measures will be supplied to the organization.
4.2 Purpose of the Measurement Plan
The project’s measurement plan is produced as one of the start-up documents to record the project’s objectives for measures collection and how it intends to carry out the program. The plan also
- Ensures that activities pertinent to the collection of project measures are considered early in the project and are resolved in a clear and consistent manner.
- Ensures that project staff are aware of the measures activities and provides an easy reference to them.
The measurement plan complements the project’s quality and project plans, highlighting matters specifically relating to measures. The measurement plan information can be incorporated into the quality and/or project plans. Information and instructions shall not be duplicated in these plans.
4.3 Format
Section 5 defines a format for the measurement plan in terms of a set of headings that are to be used, and the information required to be given under each heading. The front pages shall be the minimum requirements for a standard configurable document.
4.4 Document Control
The Measurement Plan shall be controlled as a configurable document.
4.5 Filing
The measurement plan shall be held in the project filing system.
4.6 Updating
The measurement plan may require updating during the course of the project. Updates shall follow any changes in requirements for collecting measures or any change to the project which results in change to the project WBS. The project leader/manager shall be responsible for such updates or revisions.
5 Contents of Measurement Plan
This section details what is to be included in the project’s measurement plan. Wherever possible, the measurement plan should point to existing organization standards, and so on, rather than duplicating the information.
For small projects, the amount of information supplied under each topic may amount to only a paragraph or so and may not justify the production of the measurement plan as a separate document. Instead, the information may form a separate chapter in the quality plan, with the topic headings forming the sections/paragraphs in that chapter. On larger projects a separate document will be produced, with each topic heading becoming a section in its own right. The information required in the plan is detailed under appropriate headings.
Thematic Outline for a Measurement Plan
Section 1 Objectives for Collecting Measures
The project’s objectives for collecting measures shall be described here. These will also include the relevant organization objectives. Where the author of the measurement plan is not the project leader/manager, project management agreement to these objectives will be demonstrated by the fact that the project manager is a signatory to the plan.
Section 2 Use and Users of Information
Provide information that includes
- Who will be the users of the information to be derived from the measures.
- Why the information is needed.
- Required frequency of the information.
Section 3 Measures to be Collected
This section describes the measures to be collected by the project. As far as possible, the measures to be collected should be a derivative of the core measures. If organizational standards are not followed, justification for the deviation should be provided. Project specific measures shall be defined in full here in terms of the project tasks.
A goal-question-metric (GQM) approach should be used to identify the measures from the stated project objectives. The results of the GQM approach should also be documented.
Section 4 Collection of Measures
Provide information that includes
- Who will collect each measure.
- The level within the project task against which each measure is to be collected.
- When each measure is to be collected in terms of initial estimate, re-estimates and actual measurement.
- How the measures are to be collected, with reference to proformas, tools and procedures as appropriate.
- Validation to be carried out, including details of the project specific techniques if necessary, and by whom.
- How and where the measures are to be stored—including details of electronic database/spreadsheet/filing cabinet as appropriate, how the data is amalgamated and when it is archived, who is responsible for setting up the storage process, who is responsible for inserting the data into the database.
- When, how and which data is provided to the organization measures database.
Section 5 Analysis of Measures
Provide information that includes
- How the data is to be analyzed, giving details of project specific techniques if necessary, any tools required, and how frequently it is to be carried out.
- The information to be provided by the analysis.
- Who will carry out the analysis.
- Details of project specific reports, frequency of generation, how they are generated and by whom.
Section 6 Project Organization
Describe the organization within the project that is required to support the measurement activities. Identify roles and the associated tasks and responsibilities. These roles may be combined with other roles within the project to form complete jobs for individual people. The information flow between these roles and the rest of the project should also be described.
Section 7 Project Task Structure
Describe or reference the project’s the project task structure. It should be noted that the project’s measurement activities should be included in the project task structure.
Section 8 Standards
A description of the measurement standards and procedures to be used by the project must be given, indicating which are organization standards and which are project specific. These standards will have been referenced throughout the plan, as necessary. If it is intended not to follow any of the organization standards in full, this must be clearly indicated in the relevant section of the measurement plan, and a note made in this section.