| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.3/uma.ecore" xmi:id="_7ygXoMM3EdmSIPI87WLu3g" name="metrics,_0mYYkMlgEdmt3adZL5Dmdw" guid="_7ygXoMM3EdmSIPI87WLu3g" changeDate="2006-08-29T17:19:12.494-0700"> |
| <mainDescription><h3> |
| What is a Metric? |
| </h3> |
| <p> |
| We distinguish between measure and metric.&nbsp; To clarify, let’s start by defining what is meant by measure and by |
| metric. |
| </p> |
| <ul> |
| <li> |
| <strong>Measure</strong>:&nbsp;a raw data item that is directly measured and that will be used to calculate a |
| metric.&nbsp; |
| </li> |
| <li> |
| <strong>Metric</strong>:&nbsp;an interpretation of a measure or a set of measures that you use to guide your |
| project. |
| </li> |
| </ul> |
| <p> |
| For example, recording how many test cases have passed and how many have failed are <strong>measures</strong>. |
| Interpreting what level of quality this indicates and how it reflects the team's progress within the current iteration |
| is a <strong>metric</strong>. |
| </p> |
| <h3> |
| Why Measure? |
| </h3> |
| <p> |
| Measurements will mainly help you to: |
| </p> |
| <ul> |
| <li> |
| <div style="MARGIN-LEFT: 2em" align="left"> |
| <strong>Communicate effectively</strong>. Measurement supports effective communication among team members and |
| project stakeholders.&nbsp; |
| </div> |
| </li> |
| <li> |
| <div style="MARGIN-LEFT: 2em" align="left"> |
| <strong>Identify and correct problems early</strong>. Measurement enables you to identify and manage potential |
| problems early in the development lifecycle.&nbsp; |
| </div> |
| </li> |
| <li> |
| <div style="MARGIN-LEFT: 2em" align="left"> |
| <strong>Make informed trade-offs</strong>. Measurement helps assess objectively the impact of decisions, |
| helping managers to make trade-off decisions to best meet project goals.&nbsp;&nbsp; |
| </div> |
| </li> |
| <li> |
| <div style="MARGIN-LEFT: 2em" align="left"> |
| <strong>Tune estimations</strong>. Recording schedule, progress, and expenditures for projects will help team |
| members to make more reliable estimations in the future. |
| </div> |
| </li> |
| </ul> |
| <h3 align="left"> |
| Potential Challenges |
| </h3> |
| <p align="left"> |
| There are several dangers when it comes to metrics: |
| </p> |
| <div style="margin-left: 2em"> |
| <ul> |
| <li> |
| <div align="left"> |
| They can be too costly.&nbsp;The benefit provided by the metric must exceed the cost of collecting |
| it.&nbsp;Keep your measurements simple and easy to collect. |
| </div> |
| </li> |
| <li> |
| <div align="left"> |
| They’re a poor substitute for communication.&nbsp;The best way to determine the current status of a project |
| is to ask the people involved, not to look at a report summarizing key metrics. |
| </div> |
| </li> |
| <li> |
| <div align="left"> |
| They can be misleading.&nbsp; No metric or collection of metrics is perfect.&nbsp;Furthermore, the |
| measurements upon which they are based can be manipulated by the people capturing them.&nbsp;Don’t rely |
| simply upon metrics to manage a project.<br /> |
| </div> |
| </li> |
| </ul> |
| </div></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |