PSPO Product Metrics and ROI 2 — Questions and Answers
Question 1: What is the difference between leading and lagging indicators for a Product Owner?
- Leading indicators predict future outcomes; lagging indicators confirm past results (Correct answer)
- Lagging indicators predict trends; leading indicators confirm history
- They are interchangeable terms for the same type of metric
- Leading indicators are for engineering; lagging indicators are for business
Correct answer: Leading indicators predict future outcomes; lagging indicators confirm past results
Leading indicators like trial sign-ups predict future success, while lagging indicators like quarterly revenue confirm past performance — both are useful for different decisions.
Question 2: How can A/B testing support a Product Owner's decision-making?
- By proving that new features are always better than existing ones
- By providing empirical evidence about which product variation delivers more value to users (Correct answer)
- By replacing stakeholder input in feature decisions
- By measuring individual Developer productivity
Correct answer: By providing empirical evidence about which product variation delivers more value to users
A/B testing provides empirical data about user behavior and preference, enabling evidence-based product decisions rather than relying on assumptions or opinions.
Question 3: What is user retention rate and why does it matter to a Product Owner?
- The percentage of users who continue using the product over time, indicating whether it delivers sustained value (Correct answer)
- The number of new users acquired each Sprint
- A metric tracking how long users spend on each page
- A measure of customer support ticket resolution time
Correct answer: The percentage of users who continue using the product over time, indicating whether it delivers sustained value
Retention rate reveals whether users find lasting value in the product; low retention signals that the product is not meeting user needs over time.
Question 4: What is the concept of 'cost of delay' and how should a Product Owner apply it?
- The financial cost of team overtime when Sprint goals are missed
- The value lost by not delivering a feature sooner, used to prioritize high-urgency, high-value items (Correct answer)
- The penalty for failing to meet contractual delivery dates
- The cost of running the development team without delivering features
Correct answer: The value lost by not delivering a feature sooner, used to prioritize high-urgency, high-value items
Cost of delay quantifies the opportunity cost of deferring a feature, helping the Product Owner prioritize items where delay creates the most significant value loss.
Question 5: What does 'actionable metric' mean for a Product Owner?
- A metric that executives can present in board meetings
- A metric that directly informs a decision or triggers a specific response when it changes (Correct answer)
- A metric tracked automatically by product analytics tools
- A metric that measures team velocity over multiple Sprints
Correct answer: A metric that directly informs a decision or triggers a specific response when it changes
Actionable metrics are ones where a change in the number tells the Product Owner what to do next, unlike vanity metrics that inform no specific action.
Question 6: How should a Product Owner measure the success of a newly released feature?
- By counting the number of lines of code added
- By tracking adoption, usage, and outcome metrics against pre-defined success criteria (Correct answer)
- By measuring team velocity before and after the release
- By asking the Scrum Master to evaluate team performance
Correct answer: By tracking adoption, usage, and outcome metrics against pre-defined success criteria
Feature success should be measured against pre-defined outcome metrics like adoption rate, user behavior change, or business impact — not activity metrics.
What is the difference between leading and lagging indicators for a Product Owner?