When calculating Weighted Shortest Job First (WSJF), what action should be taken?
Correct Answer: B
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. References: * WSJF - Scaled Agile Framework * Weighted Shortest Job First (WSJF) | Definition and Overview - ProductPlan * Weighted Shortest Job First - Open Practice Library
Question 37
In which Roadmap Feature bucket would a Product Manager place an add-on Feature?
Correct Answer: C
An up-sell feature is a feature that encourages customers to buy a more expensive or advanced version of a product or service, or to add additional products or services to their purchase. An up-sell feature can increase the revenue and profit per customer, and enhance the customer value proposition. An add-on feature is a type of up-sell feature that adds functionality or benefits to the existing product or service, and usually requires an extra payment or subscription. For example, a cloud storage service may offer an add-on feature of extra storage space or enhanced security for a higher fee. Reference: Feature Categories: This article from the Scaled Agile Framework explains the concept and purpose of feature categories, and how they can help product teams prioritize and communicate the value of features. It also describes the four main feature categories: new business, up-sell, operational efficiency, and retainment. Product Roadmap: Examples, Types and Key Features: This article from AltexSoft provides a comprehensive guide on product roadmaps, including their key features, common types, and examples. It also provides some tips and best practices on roadmap creation and communication.
Question 38
Which research game is primarily used to better understand Customer needs?
Correct Answer: A
Buy a Feature is a research game that involves presenting customers with a list of possible features for a product or service, and giving them a limited budget to spend on their preferred ones. This game helps to understand customer needs, priorities, trade-offs, and willingness to pay. It also encourages collaboration and discussion among customers, and generates feedback and insights for the product team. Reference: Buy a Feature: This article from the Scaled Agile Framework explains the purpose, process, and benefits of the Buy a Feature game, and provides an example of how it can be used in a SAFe context. Buy a Feature: The Game that Teaches Prioritization: This article from Innovation Games describes the rules, variations, and outcomes of the Buy a Feature game, and provides tips and resources for facilitating it. Customer Needs Analysis: Definition & Research Methods: This article from Qualtrics XM provides an overview of customer needs analysis, and discusses various research methods, including Buy a Feature, to identify and understand customer needs.
Question 39
Which aspect of the Continuous Delivery Pipeline (CDP) includes Gemba?
Correct Answer: A
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. References: * 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.
Question 40
Which aspects of a product's strategic intent can personas help define?
Correct Answer: D
Personas are fictional characters that represent the ideal customers or users of a product or service. They help product teams understand and empathize with the needs, goals, and preferences of their target segments. Personas can help define the features and benefit hypothesis of a product's strategic intent, which is the assumption that a certain set of features will deliver a specific benefit to the customers or users. By using personas, product teams can validate their feature and benefit hypothesis with real user feedback, and prioritize the features that deliver the most value and satisfaction to their personas. References: * Personas: This article from the Scaled Agile Framework explains the concept and purpose of personas, and how they can be used in a SAFe context to support customer-centricity, design thinking, and lean UX. * Strategic Intent: This article from the Scaled Agile Framework defines the concept and components of strategic intent, and how it guides the portfolio vision, lean budget guardrails, and portfolio backlog. * Feature and Benefit Hypothesis: This article from the Scaled Agile Framework describes the concept and process of feature and benefit hypothesis, and how it helps product teams test and validate their assumptions about customer value.
