SAFe-APM - SAFe Agile Product Manager (APM 6.0)

A measurement that can help drive Value Stream innovation and improvements is the percentage of Customers activating the product. This metric indicates how many Customers are actually using the product after acquiring it, and how well the product meets their needs and expectations. A high percentage of Customers activating the product means that the product delivers value and solves a problem for the Customers, and that the Value Stream is aligned with the Customer-centric mindset. A low percentage of Customers activating the product means that there is a gap between the product offering and the Customer demand, and that the Value Stream needs to innovate and improve the product design, delivery, and marketing.

References:

Value Stream KPIs - Scaled Agile Framework

The Four Most Useful Value Stream Metrics in Software

What is an example of a measurement that can be used to help drive …

An Enabler Feature is a type of feature that supports the development and delivery of future business features by extending the architectural runway, improving the infrastructure, or addressing compliance. An Enabler Feature is usually defined and prioritized by System/Solution Architects, who are responsible for designing and guiding the technical aspects of the solution. Therefore, the best stakeholder to collaborate with if a Product Manager wants to discuss an Enabler Feature for the upcoming PI is the System/Solution Architect, as they can provide the necessary technical expertise, guidance, and alignment.

References:

Enablers - Scaled Agile Framework

System and Solution Architect/Engineering - Scaled Agile Framework

PI Planning - Scaled Agile Framework

According to the Scaled Agile Framework, the Portfolio Backlog contains the highest-level portfolio epics, which are large, cross-cutting initiatives that require analysis, approval, and funding by the Lean Portfolio Management (LPM) team1. The ART Backlog contains the features, which are services provided by the system that fulfill stakeholder needs2. Features are derived from epics and are typically implemented by one Agile Release Train (ART) within one Program Increment (PI)3. Therefore, Request 1, which is an incremental innovation that can be done by one ART in one PI, should be added to the ART Backlog as a Feature. Request 2, which is a major opportunity impacting multiple stages of the Value Stream and requiring the participation of two ARTs over multiple PIs, should be added to the Portfolio Backlog as an Epic.

References:

Portfolio Backlog: This article from the Scaled Agile Framework explains the purpose, structure, and content of the Portfolio Backlog, and how it is managed by the LPM team using the Portfolio Kanban system.

Features: This article from the Scaled Agile Framework defines the concept of features, their attributes, and their relationship with epics and stories.

ART Backlog: This article from the Scaled Agile Framework describes the role, composition, and management of the ART Backlog, and how it supports the PI Planning process.