SAFe-APM Exam Dumps and Practice Questions

The most important planning question for primary research is what will be asked, because this determines the type, quality, and relevance of the data that will be collected. The research question or hypothesis should be specific, narrow, and discoverable through primary research methods, and it should align with the research purpose and objectives. The research question or hypothesis guides the choice of the research medium, the sample size and selection, and the data analysis and interpretation.

What is Primary Research?: This article from Purdue OWL defines primary research and explains the steps and considerations involved in planning and conducting primary research.

10.3: Planning Your Primary Research Project: This article from Humanities LibreTexts provides some tips and examples on how to plan a primary research project, including defining the research question or hypothesis, choosing the research method, and designing the research instrument.

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.

WSJF - Scaled Agile Framework

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

Weighted Shortest Job First - Open Practice Library

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.

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.

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.

Enablers - Scaled Agile Framework

System and Solution Architect/Engineering - Scaled Agile Framework

PI Planning - Scaled Agile Framework

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.

Design Thinking - Scaled Agile Framework

Personas - Scaled Agile Framework

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