Managing Products with Agility

Supporting the Product Owner with backlog management, stakeholder engagement, and value measurement.

5 minutes 5 Questions

Managing Products with Agility is a critical competency area within the Professional Scrum Master II (PSM II) framework that focuses on how Scrum Masters help organizations maximize the value delivered through their products. This domain emphasizes the Scrum Master's role in supporting Product Owne…

Concepts covered
Engaging Stakeholders and CustomersProduct Vision and Product Goal AlignmentAdvanced Product Backlog ManagementMeasuring Product ValueForecasting and Agile Release Planning
Test mode:
Start practice test

PSM II - Managing Products with Agility Example Questions

Test your knowledge of Managing Products with Agility

Question 1

A Product Owner hypothesizes that introducing a peer-to-peer mentoring feature will significantly boost long-term subscriber retention. The Scrum Team is unsure if developing this comprehensive capability is a wise investment of their time. They plan to run a brief experiment to gather empirical data. What is the most effective way to structure the success criteria for this experiment?

Correct Answer: Identify a specific behavioral leading indicator, like interaction with a proposed feature toggle, and outline a minimum acceptable threshold to validate the hypothesis.

The correct answer focuses on identifying a behavioral leading indicator and setting a minimum threshold because this approach provides fast, empirical data to validate whether users actually desire the feature before making a large investment.

Tracking velocity for a prototype focuses only on output and effort rather than the desired customer outcome. Tracking customer requests relies on stated preferences, which are significantly less reliable than observed user behavior. Comparing projected costs to estimated lifetime value is merely a predictive exercise that completely lacks actual empirical data.

Key concept: Validating product hypotheses using evidence-based leading indicators.

Question 2

A company has two major stakeholder groups with competing visions for a new product. The Product Owner is struggling to establish a single Product Goal because each group insists their features take highest priority. This conflict causes tension during Sprint Reviews and creates confusion regarding the product direction. What is the most appropriate approach the Scrum Master can suggest to help resolve this impasse?

Correct Answer: Facilitate a collaborative session where the Product Owner and both groups map their desired outcomes against the broader organizational strategy, focusing on identifying shared value hypotheses to shape a single cohesive path.

The correct approach is to help the Product Owner facilitate alignment by tying competing stakeholder requests back to organizational strategy to uncover shared value and establish a unified Product Goal.
Splitting capacity evenly fragments Developer focus and compromises the ability to deliver a cohesive increment. Creating multiple Product Backlogs violates the fundamental Scrum rule that a single product must have exactly one Product Backlog. Basing decisions solely on funding ignores the accountability of the Product Owner to collaboratively maximize overall product value rather than just taking orders.
The key concept tested is facilitating stakeholder alignment and effective Product Goal formulation.

Question 3

A Scrum Team builds a product used by three distinct customer segments. The Product Owner invites all segment representatives to every Sprint Review, but only one segment consistently attends. The other two segments send feedback via email weeks later. The Scrum Master notices the Product Backlog increasingly reflects only the attending segment's needs. How should the Scrum Master help the team address this situation?

Correct Answer: Coach the Product Owner to experiment with varied review formats and times that accommodate the different segments' constraints and preferences

Experimenting with varied review formats and times is the correct approach because it addresses the root cause of low attendance by adapting the Sprint Review to meet stakeholders where they are, maintaining transparency and enabling direct feedback from all segments.

Assigning dedicated liaisons introduces an intermediary that filters feedback and reduces the empirical inspection that Sprint Review provides. Rotating invitations deliberately excludes segments from Sprint Reviews, violating the principle that all relevant stakeholders should be able to inspect the increment every Sprint. Weighting backlog items by revenue is an arbitrary mechanical rule that undermines the Product Owner's accountability for value-based ordering and ignores actual user needs.

The key concept tested is stakeholder engagement and maximizing the effectiveness of the Sprint Review as an inspect-and-adapt opportunity.

More Managing Products with Agility questions
1368 questions (total)
Practice 100 questions
One session at a time, always new questions