TPMM

Identify & Populate Metrics for Progress

Decision Point has defined a set of metrics that attempt to quantify the overall risk to a given project across a wide set of program attributes that include requirements, measures of effectiveness, cost, transition agreement, transition timeline, timeline to next TRL, risk, and Technology Advancement Degree of Difficulty. Knowing where the Project falls in these metrics will give a Project Manager a better understanding of what is needed to move the Project forward.

A total Metrics Score (while subject to local consideration) may be interpreted as follows:

  • A Project that totals [> 33] is in urgent need of review for continuation (High Risk)
  • A Project that ranks [> 21 but < 32] needs Management Oversight (Moderate Risk)
  • A Project that totals [> 11 but < 20] needs periodic Management review (Low Risk)
  • A Project that totals [<10] is considered to be under the Project Manager’s control (Project "On Rails")

How The Metrics Work

Inputs:

  • Goals and objectives define direction, priorities, and change of course, if necessary.
  • Metrics for project phase should be defined by each project step to check its progress.

Control:

  • Systems Engineering Management Plan provides guidance for the systems engineering process.
  • Schedule and Budget constrain the project.

Enablers:

  • Stakeholder involvement enables the stakeholders to suggest metrics and provide guidance.
  • Control gates provide an opportunity for tracking progress.
  • Risk management suggests and uses metrics.

Outputs:

  • Metrics are the selected measures of project progress and performance.
  • Tracking documentation is a history of project progress relative to the metrics.
  • Recommended response actions to noted project problems document the recourse and rationale.
  • Technical reviews suggest metrics and review their tracking. Trade studies compare alternatives relative to the metrics.

Complete the Project Metrics Assessment

  1. Technology Advancement Degree of Difficulty – is a measure of difficulty that is a function of the ability to accomplish the intent of the Applied Research. Where would you rank your project?
  2. Risk – is defined in terms of vulnerabilities from any source to a Project’s success. The extent of the vulnerability is typically measured as impact and probability of occurance. This metric is designed to capture the extent to which those effects have been mitigated (planned for). Where does your project stand?
  3. Next TRL Achievement – is a measure of the time (in months) to next TRL. The intent of this measure is to provide an indication when time-to-market is of primary importance. How far away is achievement of the next TRL level for your project?
  4. TRL Roadmap to Transition – is a measure of the timeliness of a Project’s Transition timeline. How long is the estimated transition time for your project?
  5. Technology Transition Agreement (TTA) Initiated - is an indicator of the status of a Project’s Transition agreement and is a measure of the certainty that the Technology is on a path to be delivered and “transitioned” with all agreed-to capability, form-fit, and packaging to a DoD Acquisition Program Manager. The levels of TTA are as published by the DAU. What level of TTA has your project achieved?
  6. Phase Cost – is a gross measure of the funding needed to get the Project to the next level of maturity. The range of this value may be tailored by an S&T Enterprise as it deems appropriate to its business model. The intent of this metric is to provide a gross effort indicator when cost is of primary concern. How much will it cost to get your project to the next TRL Level?
  7. Measures of Effectiveness – is determined by the % of improvement provided by the technology Project over existing capability or new/modified required performance stated in a Capability Development Document. What measures of effectiveness do you anticipate for your project?
  8. Requirements Trace – is a measure of the extent to which a Project’s technology is being developed in direct response to a need. How would you evaluate your project?