SAFe-APM Online Practice Questions

Explanation:
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?

Explanation:
The horizon model is a framework that helps organizations balance their investments across different time horizons and types of innovation. According to the Scaled Agile Framework, there are four horizons: Horizon 0, Horizon 1, Horizon 2, and Horizon 31. Horizon 1 describes the desired state as stable solutions that deliver high value with minimal new investment. These are the core products or services that generate most of the current revenue and profit, and have a loyal customer base.
Horizon 1 solutions require continuous improvement and optimization, but not significant new investment or disruption. Horizon 1 can be further divided into two sub-horizons: Investing and Extracting2.
Reference: Horizon Planning: This article from the Scaled Agile Framework explains the concept and purpose of horizon planning, and describes the four horizons and their characteristics, challenges, and best practices.
SAFe®’s investment horizon model ― A synopsis: This article from Medium provides a summary of the SAFe investment horizon model, and illustrates how it can help organizations allocate their resources and manage their portfolio.

Explanation:
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.

Explanation:
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 C Application Programming Interface Best Practices Best Practices in API Design - Swagger

Explanation:
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.