The document discusses metrics for project management. It recommends creating a small set of key metrics focused on cost, schedule, quality and user satisfaction that provide high-level information for management. Additionally, it suggests defining operational metrics to identify specific issues and risks. The document provides guidance on establishing a metrics program, including keeping the metrics and collection cycle simple and cost-effective to support better decision making.

1. 06-Feb-2012
Group: Add metrics to your PM system
• Create a list of measurements associated with you PM
system design.
• Explain what you measure, why and what decisions a
Session 8.
certain measurement support.
Project control – Metrics,
templates, tools
Measurement in software development Management Measures
• Purpose • Small number of measures that management can
– Improve communication monitor to continuously evaluate progress and identify
– Track specific objectives issues.
– Identify and correct problems early
– Four bottom line measures: Cost, Schedule, Quality and User
– Support and justify decisions satisfaction
– Assist contract management (SLA)
• These measures tell you if “your oil is low”
• Measurement allows to drill down from symptoms to the
actual cause.
• Types of metrics:
– Management
– Operation
Operational Measures Metrics set
• Measures to identify cause of issue, risk potential or • Progress
impact of problem • Effort
• These measures show “why you are losing oil” • Costs
• Trouble
• Requirements
• Software size
• Performance
• Training
• ….
1

2. 06-Feb-2012
Keep the Metrics Simple Keep the Metrics Cycle Short
• The goal of a metrics program is better management not • Problems and issues are time sensitive; metrics must
measurement. identify problem, risk triggering or impacts as close to
• Each metric must be directly related to a (management) occurrence or condition as possible.
issue that you wish to address – Wrong action may be far worse than no action
– Don’t collect everything, hoping that something interesting will • If the information isn’t current, it is at best, worthless.
show up.
Keep the Metrics Collection Metrics Program Essentials
Cost Down
1. Document software process
• Software metrics collection program costs should not
exceed 5% of the development cost. 2. Set reasonable goals for each of the metrics you are
collecting, and try to achieve them.
• Automated tools may help collect many metrics.
– Why do we use a certain metrics set?
• Always consider useful data already being captured
– Quantitative targets should be set
– for example, a time reporting system with a good work break-down
structure can be used to capture costs – Actions should be set by triggers and should be staged.
– a good configuration management tool can collect requirements Examples:
instability data. • A 5% drop/increase in a certain measure will trigger the
measure/issue to be flagged and a risk analysis.
• A 30% drop initiates a management review
• A 60% drop forces mitigation strategy
Actions Based on Metrics Focus on a Small Set of Metrics
• Monitor trends, not just values • Tendency is to collect too much information over time
– Even small deviations from the last measure may be significant even
though the basic value may be within bounds. which can’t be analyzed.
– If a trend is not heading where you want it to go, go investigate the – Additional metrics do not always provide sufficient additional
causes, evaluate the situation, and make the necessary corrections.
information to justify their expense.
• Never take action based on a single metric
– A negative trend or deviant value likely has many possible causes. – Metrics will not replace management and are most effectively
• the “obvious” problem is usually not the underlying cause. used to provide data about potential problem areas to focus
– A pilot wouldn’t shut down the engine of an aircraft based on a bad engine
indicator light. management attention.
– first confirms that the problem is not with the indicator light. – While metrics will provide information, the metric does not tell a
manager what to do with
2