Task: Determine Metrics To Track
Determine who captures which metrics and when they are captured.
Disciplines: Asset Governance
Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    Optional:
    • None
    Outputs
      Main Description

      In this task the Reuse Strategy should be evaluated regarding that the metrics the enterprise wants to track.

      There are several kinds of metrics to track, including metrics managed by the repository, metrics entered by Asset Owners or Producers, and metrics entered by Asset Consumers.

      Since collecting metrics can be distributed amongst many roles and points in software development, the asset rules and policies and other governance documents should be updated with the results of this task. A key value of defining metrics early in the effort is to establish a common baseline for what a metric means, who creates the metrics, and where they are captured. Without establishing this baseline the metrics are too vague and left to individual interpretation. This lacks clarity and does nothing to help the asset reuse work roll forward.

      This task of defining how the asset program will be measured is a core requirement to the success of the asset efforts to continue.

      A sampling of metrics is introduced below for each of the categories of metrics.

      Quantitative Metrics Tracked By The Repository

      • Number of downloads for an asset
      • Searches and views
      • Number of assets in repository of a given type, or state
      • Number of assets submitted

      Quantitative Metrics Submitted by Asset Owners or Producers

      • Level of effort to create the asset
      • Level of anticipated effort for an Asset Consumer to reuse an asset

      Quantitative Metrics Submitted By Asset Consumers

      • Actual level of effort to use the asset
      • Project/team/engagement where the asset was used

      Qualitative Metrics Submitted By Asset Consumers

      • Reusability rating (scored with stars)
      • Textual feedback

      Derived Metrics

      These are metrics that are generally derived by management and project leads.

      • Number of repository accesses over a period of time
      • Number of asset submissions over a period of time
      • Number of defects submitted for a given asset
      • Number of assets used over a period of time
      • Return on investment for the repository
      • Level of reuse on a given project
      • Productivity gains and ROI realized by using assets on a project

      The metrics described here are usage-oriented metrics. They focus on the activities around using an asset. Another set of metrics describe the cost side of assets. When brought together, they provide support for understanding the value of assets to the enterprise. These cost-side metrics will typically be found in a portfolio management tool.

      Other metrics in terms of identifying the value of assets as they are used include:

      • Reuse costs (time to use, modify, etc.)
      • Time saved from using the asset

      Jeffrey Poulin's work on Measuring Software Reuse (Addison Wesley, 1997, ISBN: 0-201-63413-9) describes some key metrics to start with and grow into.

      Steps
      Determine the Scope of the Metrics to Capture
      The metrics may be captured for a given project, a community, or for the entire enterprise.
      Determine the Recipients of the Metrics to Capture

      The target individuals, or teams, who will be receiving the metrics should be identified. For example the target individuals may be a project leader, or may be the Sponsor.

      Determine Frequency of Capturing Metrics
      Some metrics may be captured more easily from the repository whereas other metrics may require some digging and calculation work. In this step the manager determines how is gathering the metrics, and what will they need to do in order to collect them.
      Determine Who Will Capture the Metrics and How
      Some metrics may be captured more easily from the repository, whereas other metrics may require some digging and calculation work. In this step, the manager determines who is gathering the metrics, and what they will need to do in order to collect them.
      Key Considerations

      Impact/Influence on the ABD process: