What is the most important planning question for primary research?
Correct Answer: C
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. Reference: 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.
Question 32
When dealing with a complex product, what is best defined as a secondary persona?
Correct Answer: A
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?
Question 33
Which key job function differentiates a Product Manager from a Product Owner (PO)?
Correct Answer: D
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
Question 34
What is the most important information to communicate in a product Vision?
Correct Answer: A
A product vision is a description of the future state of the product and what problems it tries to solve or what ambitions it tries to fulfill. The most important information to communicate in a product vision is how life/work will improve by using this solution. This information captures the value proposition and the benefit hypothesis of the product, which reflect the needs and expectations of the customers and the stakeholders. This information also inspires and motivates the people who work on the product, as well as the potential users of the product. This information sets the direction and the purpose of the product, and guides the development and delivery of the features and capabilities. Reference: Vision - Scaled Agile Framework Solution Vision - Scaled Agile Framework Product Vision | Agile Product Management
Question 35
What criterion must be satisfied before a Feature can flow from the analysis state to the backlog state on an ART Kanban?
Correct Answer: D
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. References: * 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 ...
