Skip to content

Program Value Metrics

Short Tip: The process of defining and periodically assessing the value of a program.

What is it?

It is the process of initially defining value metrics associated with a set of related products (program), as well as their measurement on a periodic basis.

The program’s value metrics should be fed by each product’s individual metrics in order to consolidate the former into value metrics for the business.

Why use it?

Value metrics are important to measure the effective impact of a solution on the problem initially addressed. Measurement at the program level, not just at the product level, provides an integrated and more comprehensive view, in addition to being the interface with the portfolio level.

How to use it?

The process is divided into defining the value metrics and monitoring them, and consists of the following steps:

  • Understanding, for the products in the program, the value metrics currently used, as well as their update policy;
  • Establish with the Product Owners (PIM-Go© Agile) and Initiative Leaders (PIM-Go© Hybrid) a discussion about potential metrics that would be relevant for capturing the overall value of the program;
  • Based on these proposed metrics, define the ones that will be used;
    • It is advisable that the set of selected metrics mix lead (close to real-time) and lag (periodic updating) characteristics;
  • Identify how to update these metrics based on information generated for the product;
    • If there are program metrics whose product lacks such information, request the inclusion of an action into the Product Backlog in order to capture this data with the necessary frequency;
  • Start monitoring the value metrics and hold a discussion with the Product Owners (PIM-Go© Agile) and Initiative Leaders (PIM-Go© Hybrid) about the results achieved. More than an information repeater, program metrics should enable a discussion on ways to improve existing products or even new insights to create new products.

Additional Information