The frequency of data collection also needs to be specified. Measurements should be taken frequently enough to identify problems, and allow their correction prior to generating substantial scrap, creating substantial rework, or missing critical milestones. For example, if an organization cannot afford to lose the month-long effort of five individuals working on a project prior to identifying a problem in product production, measurements frequency must be substantially more than monthly. In determining the collection frequency, do not forget to include the time required to process the data into measurements and metrics, and to get the metrics into decision-makers hands. The following example of how the steps are used in a measurement program is based on the idea that an organization has been tasked to deliver a new software release within 120 days.
Define information needs.
Suppose one of the goals of the organization was to deliver the product on time. Define metrics and analysis methods to address information needs. The metric used may be staff hours available per day. The analysis method chosen could be the use of X-Bar and R charts to determine if the number of hours delivered per day is within statistical control. The term staff hours available per day should be explicitly defined so that everyone on the project understands what is meant by an available staff hour.