Free SAFe-APM Practice Test Questions and Answers (2026)

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

Design Thinking is a creative process that involves empathizing with customers, defining the

problem, ideating possible solutions, prototyping, and testing. Design Thinking can help API design

and development by ensuring that the APIs are user-centric, meet the needs and expectations of the

customers, and deliver value to the business. Design Thinking can also help API design and

development by fostering collaboration, experimentation, and feedback among the stakeholders,

such as product managers, developers, and customers.

Reference:

Design Thinking - Scaled Agile Framework

How to Design an API – Application Programming Interface Best Practices

Best Practices in API Design - Swagger

One of the strengths of qualitative research is that it can be applied to a large number of people, as it

does not require a fixed sample size or a predefined set of questions. Qualitative research can use

various methods, such as interviews, focus groups, observations, or document analysis, to collect

data from different sources and contexts. This allows researchers to explore a wide range of

perspectives, experiences, and meanings, and to generate rich and diverse insights.

Reference:

23 Advantages and Disadvantages of Qualitative Research

5 Strengths and 5 Limitations of Qualitative Research

The chasm is the gap in the technology adoption lifecycle between the early adopters and the early

majority. The early adopters are visionaries who are open to trying new technologies, whereas the

early majority are pragmatists who are more cautious and skeptical. The chasm occurs due to the

different expectations and requirements of these two groups. A product that appeals to the early

adopters may not appeal to the early majority, who value reliability, compatibility, and convenience

over novelty and differentiation. Therefore, a product needs to cross the chasm by finding a niche

market, establishing a clear value proposition, and creating a strong word-of-mouth.

Reference:

Crossing the Chasm & Scale Your SaaS: This article from Userpilot provides a practical guide on how

to cross the chasm and scale a SaaS product, with examples and tips on finding product-market fit,

defining a beachhead market, and creating a whole product.

Crossing the Chasm in the Technology Adoption Life Cycle: This article from Business to You explains

the concept and purpose of the technology adoption lifecycle and the chasm, and how they can help

marketers understand and target different customer segments.

A milestone is a specific point in time that marks a significant event or achievement for the ART or

Solution Train. A milestone can indicate a market window occurrence during a PI, which is a limited

period of time in which a product or service can be launched to gain a competitive advantage or

meet a customer demand. A milestone can help the ART or Solution Train align their delivery with

the market window, and communicate their progress and readiness to the stakeholders.

Reference:

Milestones: This article from the Scaled Agile Framework explains the concept and purpose of

milestones, and describes the four types of milestones: Program Increment (PI), Fixed-Date,

Learning, and Benefits.

ART Planning Board: This article from the Scaled Agile Framework describes the role and structure of

the ART Planning Board, and how it supports the PI Planning process and the Program Board.

ART Planning Board - PI Planning: This article from Ivar Jacobson International provides practical

advice and examples of how to use the ART Planning Board during the Management Review, and

what to look for in terms of market windows, dependencies, risks, and objectives.

Buy a Feature is a research game that is primarily used to better understand the priorities of Solution

requirements. Buy a Feature is a collaborative prioritization technique that involves giving

participants a fixed amount of virtual money and a list of features or requirements with different

costs. The participants then have to decide which features or requirements they want to buy, either

individually or in groups. The game reveals the p

, trade-offs, and consensus of the

participants, as well as the relative value and importance of each feature or requirement.

Reference:

Buy a Feature - Scaled Agile Framework

Buy a Feature - Innovation Games

What Innovation Game is primarily used to better understand the priorities of Solution

requirements?

Time criticality is one key component of Cost of Delay (CoD), which is the money or value that will be

lost by delaying or not doing a job for a specific time period relative to other jobs. Time criticality

reflects the urgency or sensitivity of a job to time, and how its value changes over time. For example,

a job that has a fixed deadline, a seasonal demand, or a high risk of obsolescence has a high time

criticality, and its CoD increases rapidly as time passes. A job that has a stable demand, a low risk of

competition, or a long-term benefit has a low time criticality, and its CoD increases slowly or remains

constant over time.

Reference:

WSJF: This article from the Scaled Agile Framework explains the concept and purpose of Weighted

Shortest Job First (WSJF), which is a prioritization model that uses CoD and job duration to sequence

jobs for maximum economic benefit. It also describes the four components of CoD: user or business

value, time criticality, risk reduction and/or opportunity enablement, and job size.

Cost of Delay - Scaled Agile Framework: This article from the Scaled Agile Framework defines CoD as

the numerator in WSJF prioritization, and provides some examples of how to estimate CoD for

different types of jobs.

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

Weighted Shortest Job First (WSJF) is a prioritization model used to sequence work for maximum

economic benefit. It is calculated by dividing the cost of delay by the job duration or size. To estimate

the cost of delay, three factors are considered: user and business value, time criticality, and risk

reduction or opportunity enablement. To estimate the job duration or size, a relative scale such as

Fibonacci is used. The highest value in the Fibonacci scale is set as the “ceiling” and the lowest value

is set as the “floor”. The items are then scored by comparing them to the ceiling and the floor, and

assigning them the closest Fibonacci number. The WSJF score is then obtained by dividing the cost of

delay score by the job duration or size score. The items with the highest WSJF score are prioritized

first.

Reference:

WSJF - Scaled Agile Framework

Weighted Shortest Job First (WSJF) | Definition and Overview - ProductPlan

Weighted Shortest Job First - Open Practice Library

Market segmentation is the process of dividing a market into distinct groups of customers who have

similar needs, p

, or behaviors. Market segmentation helps enterprises identify and target

the most valuable and profitable customer segments, design and deliver solutions that meet their

needs, and optimize their marketing strategies and campaigns. However, market segmentation is not

only based on quantitative factors, such as size, growth, and profitability, but also on qualitative

factors, such as values, mission, and vision. A market segment should align with the enterprise’s

values and mission, which reflect its purpose, identity, and culture. A market segment that aligns

with the enterprise’s values and mission will help the enterprise achieve its strategic goals, create a

positive brand image, and build trust and loyalty with customers.

One of the characteristics of effective market segmentation is that the segment should be valuable

enough to be economically feasible. This means that the segment should have enough potential

customers who are willing and able to pay for the products or services offered by the enterprise. The

segment should also generate enough revenue and profit to cover the costs of marketing,

production, and distribution. The segment should also have a positive impact on the enterprise’s

return on investment (ROI) and net present value (NPV). A segment that is not valuable enough to be

economically feasible will not be sustainable or profitable for the enterprise.

Reference:

Customer Centricity - Scaled Agile Framework

Advanced Topic - SAFe for Marketing - Scaled Agile Framework

What is one consideration when evaluating the fit for a market segment?

5.4 Essential Factors in Effective Market Segmentation

A product vision is a statement that describes the desired outcome and value proposition of a

solution. It helps guide the development of the solution by providing a clear and compelling

direction. A product vision also helps drive a solution roadmap, which shows the planned features

and milestones for the solution over a timeline. A product vision is part of the solution intent, which

is the repository of the current and intended solution behavior and design.

Reference:

Solution Intent

Solution Vision

Roadmap

Solution Management

The strategic sweet spot of a company is where it meets customer’s needs in a way that rivals can’t,

given the context in which it competes12. It is where the company’s capabilities match customer

needs in a way that the competition can’t. Finding the strategic sweet spot is a key challenge of

strategic thinking and a source of competitive advantage.

Reference:

How to find your strategic sweet spot and why it matters

The Strategic Sweet Spot - Harvard Business Review

Thank you for your visit.

The ART Sync is a weekly event that brings together the representatives of the teams and

stakeholders of an Agile Release Train (ART) to review the progress and status of the current Program

Increment (PI). The ART Sync tracks the progress of the ART toward meeting the PI Objectives by

using various metrics and indicators, such as the PI burnup chart, the team and ART predictability

measures, the feature completion report, and the dependencies and risks status. The ART Sync also

provides an opportunity to identify and resolve any impediments, issues, or blockers that may affect

the PI delivery.

Reference:

ART Sync: This article from the Scaled Agile Framework explains the purpose, agenda, and

participants of the ART Sync, and how it supports the alignment, collaboration, and execution of the

ART.

PI Objectives: This article from the Scaled Agile Framework defines the concept and attributes of PI

Objectives, and how they can be used to align and measure the outcomes of an ART or Solution

Train.

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

A story map is a customer-centric requirement artifact that represents the user journey and the

features that support it. A story map is a visual tool that helps to organize and prioritize user stories

based on the user goals, activities, and tasks. A story map also helps to align the stakeholders on the

scope, value, and dependencies of the product, and to plan the releases and iterations.

Reference:

Story Mapping - Scaled Agile Framework

What are some example artifacts from product definition?

User Story Mapping: A Complete Guide | Miro

The benefit hypothesis and acceptance criteria are the criteria that must be satisfied before a Feature

can flow from the analysis state to the backlog state on an ART Kanban. The benefit hypothesis and

acceptance criteria are part of the definition of a Feature, which represents a solution functionality

that delivers business value and fulfills a stakeholder need. The benefit hypothesis states the

expected outcome and benefit of implementing the Feature, while the acceptance criteria define the

conditions that must be met for the Feature to be accepted by the stakeholders. The benefit

hypothesis and acceptance criteria help to clarify the scope, value, and quality of the Feature, and to

guide the implementation and validation of the Feature.

Reference:

Features and Capabilities - Scaled Agile Framework

ART and Solution Train Backlogs - Scaled Agile Framework

Which two criteria must be satisfied before a Feature flows from …