SAFE-APM Practice Questions

The value of a market segment is determined by the potential revenue and profit that can be

generated from selling products or services to that segment. One of the key factors that influences

the value of a market segment is the amount customers are willing to pay for products or services,

which reflects their perceived value and price sensitivity. Customers who are willing to pay more for

products or services that meet their needs and p

are more valuable than customers who

are willing to pay less or switch to cheaper alternatives. Therefore, understanding the customer’s

willingness to pay is essential for setting optimal prices and maximizing the value of a market

segment.

Reference:

Market Segmentation: Definition, Example, Types, Benefits: This article from Investopedia explains

the concept and purpose of market segmentation, and describes the four primary types of market

segmentation: demographic, geographic, psychographic, and behavioral.

Value-based Market Segmentation – Divide Markets into Value Categories: This article from

Marketing Insider provides a detailed guide on how to conduct a value-based market segmentation,

which is based on the actual value perceived and delivered to customers. It also discusses the

benefits and challenges of value-based market segmentation, and provides some examples and best

practices.

Market Segmentation: Definition, Types, Benefits, & Best Practices: This article from Qualtrics XM

provides an overview of market segmentation, and discusses the benefits and best practices of

market segmentation for businesses. It also provides some examples and tips on how to segment

markets effectively.

A secondary persona is a type of persona that represents another user of the primary interface who

can be accommodated as long as the targeted persona’s experience is not compromised. A

secondary persona is not the main focus of the product design, but still has some needs and

expectations that should be considered. A secondary persona can help to identify additional

features, functionalities, or scenarios that can enhance the product value and usability, without

sacrificing the primary persona’s satisfaction.

Reference:

Design Thinking - Scaled Agile Framework

Personas - Scaled Agile Framework

When dealing with a complex product, a secondary persona could be best defined as what?

Gemba is a Japanese term that means “the real place” or “the place where value is created”. In the

context of the CDP, Gemba refers to the practice of going to the source of customer needs and

feedback, and observing and learning from them. Gemba is an integral part of Continuous

Exploration (CE), which is the first aspect of the CDP that drives innovation and fosters alignment on

what should be built. CE involves applying Customer Centricity and Design Thinking to understand

and create alignment on new development opportunities, and validating them with customers using

hypothesis-driven experiments.

Reference:

Continuous Exploration: This article from the Scaled Agile Framework explains the purpose, process,

and benefits of CE, and how it uses Gemba, design thinking, and lean startup methods to explore the

market and customer needs, and define a vision, roadmap, and set of features for a solution.

Gemba Walk: How to Drive Continuous Improvement in Manufacturing with Connected Work: This

article from Parsable describes how Gemba walks can help manufacturing leaders and teams identify

and solve problems, improve processes, and increase customer value. It also provides some tips and

best practices for conducting effective Gemba walks using connected worker technology.

Journey maps are a design thinking tool that help visualize the steps, interactions, and emotions of a

user as they go through a process or a service. Journey maps can help redesign work processes by

identifying the pain points, opportunities, and gaps in the current state, and by generating ideas for

improving the user experience and value proposition in the future state. Journey maps can also help

communicate the user needs and expectations to the stakeholders and align them on a common

vision and goal.

Reference:

Journey Maps - Scaled Agile Framework

Journey Mapping 101 | Nielsen Norman Group

Journey Mapping: The Ultimate Guide | Miro

Journey Mapping: How to Create One and Why It’s Important

One of the key job functions that differentiates a Product Manager from a Product Owner (PO) in

SAFe® is prioritizing the backlog. A Product Manager is responsible for defining and prioritizing the

features and capabilities that deliver value to the customers and the business. A Product Manager

owns and maintains the Program Backlog, which is the single source of truth for the work that needs

to be done by the Agile Release Train (ART). A Product Owner, on the other hand, is responsible for

defining and accepting the user stories that implement the features and capabilities. A Product

Owner owns and maintains the Team Backlog, which is the subset of the Program Backlog that the

Agile Team works on. A Product Owner collaborates with the Product Manager to align the Team

Backlog with the Program Backlog and the Vision.

Reference:

Product and Solution Management - Scaled Agile Framework

Product Owner (PO) Sync - Scaled Agile Framework

SAFe Product Manager vs Product Owner - Striking Differences - KnowledgeHut

Primary data is information collected through original research by the marketer or researcher

themselves. Primary data is used to test hypotheses, which are tentative statements or assumptions

about the relationship between variables or the outcome of an experiment. Testing hypotheses helps

to validate or invalidate the assumptions and predictions made by the marketer or researcher, and to

measure the effectiveness and impact of their product or service.

Reference:

Primary Data - Types, Methods and Examples: This article from Research Method defines primary

data, explains its types and methods, and provides some examples of primary data collection and

analysis.

[Hypothesis Testing]: This article from the Scaled Agile Framework describes the concept and process

of hypothesis testing, and how it helps to evaluate the value proposition and assumptions of a

product or service using experiments and feedback.

According to the SAFe® Agile Product Management APM (6.0) documents and learning resources,

Business Owners are key ART stakeholders who have the primary business and technical

responsibility for return on investment (ROI), governance, and compliance. They are critical for

evaluating fitness for use and actively participating in solution development. They can provide

current business feedback to guide feature enhancements by assessing the value proposition, the

competitive advantage, and the expected market share of the features. They can also help align the

features with the product vision and roadmap, and prioritize them based on the WSJF method.

Reference:

Business Owners - Scaled Agile Framework

Customer Centricity - Scaled Agile Framework

WSJF - Scaled Agile Framework

According to the SAFe® Agile Product Management APM (6.0) documents and learning resources,

market segment value is the total value of a specific market segment for a given solution. It is

calculated by multiplying the number of potential customers in the segment by the average revenue

per customer and the expected market share. The expected market share depends on several factors,

such as the value proposition, the competitive advantage, and the number of existing competitors.

Therefore, the number of existing competitors is a factor that must be included when building a

model of market segment value.

Reference:

Agile Product Management - Scaled Agile Framework

Customer Centricity - Scaled Agile Framework

5.4 Essential Factors in Effective Market Segmentation

According to the SAFe® Agile Product Management APM (6.0) documents and learning resources,

innovation context type refers to the level of uncertainty and risk associated with the innovation.

There are four types of innovation context: portfolio, solution, feature, and business agility. Solution

context type is the most complex and uncertain type, as it involves creating integrated, end-to-end

products and service offerings that solve complex market problems across trains. Solution context

type requires a high degree of collaboration and alignment among multiple teams and stakeholders,

as well as frequent experimentation and validation of assumptions.

Reference:

SAFe Innovation Framework for Lean Enterprises: What to Know

Solution Context - 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.

Reference:

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.