Try 10 focused PSPO I questions on Managing Products with Agility, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PSPO I |
| Topic area | Managing Products with Agility |
| Blueprint weight | 25% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Managing Products with Agility for PSPO I. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 25% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Managing Products with Agility
A Product Owner’s team has delivered a new analytics dashboard over three Sprints. Usage of the dashboard has increased, but the expected business outcome—higher customer renewal rates—has not changed. Sales stakeholders now want two more dashboard reports added immediately, while the Developers say they could instead build a small alerting experiment next Sprint to test whether timely prompts influence renewals. The Product Goal is to improve customer renewals. What is the best Product Owner action?
Best answer: A
What this tests: Managing Products with Agility
Explanation: When output is increasing but the desired outcome is not, the Product Owner should improve learning by testing the underlying value assumption. Reordering the Product Backlog toward a small experiment tied to the Product Goal is the best way to gather evidence and adapt based on results.
The key concept is learning about value through empiricism, not simply producing more output. In this scenario, the Scrum Team already delivered more dashboard capability and saw higher usage, but the business outcome did not improve. That means the Product Owner should inspect the evidence, question the assumption that more reports drive renewals, and order the Product Backlog to learn what actually changes customer behavior.
A small alerting experiment is useful because it creates a Done Increment that tests a specific value hypothesis connected to the Product Goal. The Product Owner remains accountable for ordering the Product Backlog, while stakeholders and Developers provide input. Continuing the roadmap or optimizing usage without testing the value assumption prioritizes output over learning.
The best Product Owner action is the one that increases evidence about customer value and enables adaptation.
This uses empiricism to learn whether a different product change improves the desired outcome, while keeping Product Backlog ordering with the Product Owner.
Topic: Managing Products with Agility
A Product Owner has a Product Goal to reduce inbound support calls by 20% through a self-service portal. After four Sprints, portal visits are up 45% and new feature usage is up 30%, but support-call volume is unchanged and task completion for key customer actions fell from 78% to 52%. In the Sprint Review, support managers report users get stuck, while a sales executive asks for more promotional features to drive traffic. What is the best action?
Best answer: C
What this tests: Managing Products with Agility
Explanation: The Product Owner should act on evidence that the current approach is not improving the desired outcome. In Scrum, metrics should inform Product Backlog ordering, possible Product Goal adaptation, and transparent stakeholder communication rather than preserving a plan or deferring to stakeholder pressure.
This scenario shows a clear mismatch between output indicators and outcome evidence. More visits and feature usage do not matter if the Product Goal is reducing support calls and users are failing key tasks. The Product Owner is accountable for maximizing product value and for effective Product Backlog management, so the next step is to reorder the Product Backlog around the strongest evidence, inspect whether the current Product Goal or the path toward it still makes sense, and communicate that reasoning transparently to stakeholders.
In Scrum, empirical product decisions should be guided by:
The closest trap is treating traffic growth as sufficient success when the actual outcome is not improving.
This uses outcome evidence to maximize value, supports empirical adaptation, and keeps Product Backlog decisions with the Product Owner.
Topic: Managing Products with Agility
A Product Owner for an invoicing product has this Product Goal: reduce invoice disputes for midsize customers. At the Sprint Review, the Scrum Team learns:
What should the Product Owner order first in the Product Backlog?
Best answer: D
What this tests: Managing Products with Agility
Explanation: The best choice uses customer feedback, support data, and a compliance constraint to inform Product Backlog ordering while keeping accountability with the Product Owner. It targets the clearest evidence of value and Product Goal progress, while reducing legal risk and creating learning from the next Increment.
Stakeholders and customers should provide feedback, constraints, domain insight, and value evidence that inform Product Owner decisions. In this case, the strongest evidence is the support data and customer feedback showing a major source of disputes, which directly relates to the Product Goal. The compliance input is also important, but it is a constraint to respect, not a handoff of ordering authority.
A sales request may still matter, but it is weaker than evidence pointing to the most important current value problem.
It uses customer evidence and stakeholder constraints to inform ordering while preserving the Product Owner’s accountability for maximizing value.
Topic: Managing Products with Agility
A Sprint has ended with one Done Increment for an internal ordering product. The Product Owner also has new customer usage data, two sales stakeholders have conflicting requests, and a director wants the Sprint Review reduced to a slide-based status update so leaders can “approve” the Sprint. What is the best action for the Product Owner?
Best answer: C
What this tests: Managing Products with Agility
Explanation: The Sprint Review is not a status meeting or approval gate. The best action is to use the Done Increment, stakeholder input, and current evidence to inspect the outcome of the Sprint and decide what product adaptations make sense next.
In Scrum, the Sprint Review is a collaborative working session where the Scrum Team and stakeholders inspect the outcome of the Sprint and determine future adaptations. That means looking at the actual Done Increment, discussing what was learned, considering current market or customer evidence, and updating product direction as needed. The Product Owner remains accountable for effective Product Backlog management, but the Review should actively involve stakeholders in inspecting value and informing next decisions.
In this situation, the strongest response is to center the conversation on:
Treating the event as a status update, sign-off session, or substitute Retrospective misses its purpose of empirical product adaptation.
A Sprint Review is a working session to inspect the Sprint outcome with stakeholders and determine the most valuable future adaptations.
Topic: Managing Products with Agility
A Product Owner is preparing for a major trade show in three months. Sales wants to announce 12 specific features for that date. After two Sprints, customer feedback shows one security capability is now critical and two planned features may no longer add much value. Executives ask the Product Owner to lock scope now so stakeholders have certainty. What is the best action?
Best answer: A
What this tests: Managing Products with Agility
Explanation: The best action is to treat the trade show plan as a forecast, not as a fixed-scope promise. The Product Owner should use current evidence, communicate uncertainty transparently, and adapt the Product Backlog as learning changes what is most valuable.
In Scrum, release planning is based on empiricism rather than false certainty. A Product Owner can discuss likely timing and likely scope, but those remain forecasts that should be updated as Done Increments, stakeholder feedback, and market learning provide new evidence. In this scenario, new feedback already changes what appears most valuable, so locking all 12 features would ignore evidence and reduce the ability to maximize value.
A sound approach is to:
The closest trap is treating stakeholder pressure for certainty as a reason to make a promise Scrum cannot honestly support.
Release planning in Scrum is empirical forecasting, so the Product Owner should communicate likely outcomes and adapt scope when new evidence changes value.
Topic: Managing Products with Agility
A Product Owner is given this statement: “Increase paid conversion in the student segment this year by reducing onboarding abandonment.” It describes a desired business outcome, may guide Product Backlog ordering, and does not prescribe a specific feature or quantity of work. What is this best described as?
Best answer: C
What this tests: Managing Products with Agility
Explanation: This is a business objective because it states a desired outcome tied to business results, not a particular feature, opinion, or amount of delivery. In PSPO I terms, the Product Owner should use such outcomes to make value-focused decisions.
A business objective expresses the result the organization wants to achieve, such as better conversion, retention, revenue, or cost reduction. In the stem, the statement focuses on improving paid conversion by reducing onboarding abandonment, which is an outcome. That makes it useful for Product Owner decisions because it helps evaluate which Product Backlog options are most likely to maximize value.
By contrast, a stakeholder request would be a specific ask from a person or group, an output target would describe how much work to deliver, and an internal preference would reflect what people inside the organization happen to like. The key distinction is outcome over request, opinion, or volume.
It defines an outcome the organization wants to achieve and can use to guide value decisions without prescribing a specific solution or output.
Topic: Managing Products with Agility
At a Sprint Review, the Scrum Team presents a Done Increment for a new checkout flow. Stakeholders begin asking for a formal approval decision before any release discussion, and one director requests a status slide deck instead of discussing customer pilot feedback and market changes. What is the most appropriate next step?
Best answer: D
What this tests: Managing Products with Agility
Explanation: The Sprint Review is used to inspect the outcome of the Sprint with stakeholders and determine future adaptations. The right next step is to discuss the Done Increment, feedback, and changing conditions so the Product Backlog can be updated empirically.
The core concept is that the Sprint Review is a working session for inspection and adaptation. Because the Increment is already Done, the Scrum Team and stakeholders should use the event to examine what was achieved, review feedback and current conditions, and decide what product adaptations make sense next. That may lead to Product Backlog changes and updated forecasts, but it does not require a formal approval gate.
Treating the Sprint Review as a sign-off meeting, acceptance ceremony, or status presentation reduces transparency and delays learning. Scrum uses the event to gather evidence and improve future product decisions, not to obtain permission for the Increment to count as complete. The key takeaway is that stakeholder collaboration informs adaptation; it does not replace empirical review with approval bureaucracy.
A Sprint Review is a collaborative inspection-and-adaptation event, not a sign-off gate or status meeting.
Topic: Managing Products with Agility
A Product Owner forecasted that a new subscription-management capability might be ready for release in about 3 months. After the latest Sprint Review, stakeholders saw a usable Increment, requested changes based on what they learned, and the Product Backlog was reordered. Before updating the release expectations, which evidence should the Product Owner inspect first?
Best answer: C
What this tests: Managing Products with Agility
Explanation: Release expectations in Scrum are forecasts, so they should be updated using empirical evidence. The strongest evidence is what has actually been completed in Done Increments and how that progress compares with the current ordered Product Backlog after new learning and feedback.
Scrum uses empiricism for forecasting under uncertainty. When a Product Owner updates release expectations, the best evidence is the usable outcome already produced and the current understanding of what remains. In this scenario, stakeholders inspected a usable Increment, learned from it, and the Product Backlog changed, so the forecast should be based on progress shown by Done Increments against the newly ordered Product Backlog.
That evidence is stronger because it reflects:
A task plan, started work, or an earlier announced date may help conversations, but they are not the most reliable empirical basis for updating a release forecast.
Release expectations should be updated from usable results and the latest Product Backlog reality, not from plans or work in progress.
Topic: Managing Products with Agility
A Product Owner is updating a release forecast after a Sprint Review.
Backlog state
Stakeholders now say entering the new market before November is more valuable than holiday promotions, and they ask whether the October 15 release is certain.
What is the best Product Owner response?
Best answer: A
What this tests: Managing Products with Agility
Explanation: Release planning in Scrum is empirical. The Product Owner should adapt Product Backlog order based on stakeholder needs and market timing, then revise the release forecast using the current ordered backlog and what is actually Done. A forecast is not a commitment.
The key concept is empirical release planning. Stakeholder input and market timing can change what is most valuable, so the Product Owner should reorder the Product Backlog accordingly. But release decisions should be grounded in transparent evidence: only Done work is a reliable basis for what can be released now, and the remaining ordered backlog supports a forecast for what may be released later.
In this situation:
The closest distractors confuse planning with commitment or treat unfinished work as if it were complete.
This uses stakeholder input and market timing to reorder for value while basing release planning on Done work and transparent forecasting, not certainty.
Topic: Managing Products with Agility
A Scrum Team presents a Done Increment in the Sprint Review. During the discussion, stakeholders provide useful market feedback and ask the Product Owner to wait for their formal approval before changing release plans or Product Backlog ordering. What is the best response?
Best answer: D
What this tests: Managing Products with Agility
Explanation: The Sprint Review is an inspection-and-adaptation event. A Done Increment is already usable because it meets the Definition of Done, and stakeholder feedback should inform Product Backlog adaptation rather than act as a formal approval gate.
In Scrum, the Sprint Review is a working session to inspect the outcome of the Sprint and determine future adaptations. It is not a formal sign-off meeting, a status presentation, or an acceptance ceremony. In this scenario, the important result is the stakeholder feedback and market information, which can help the Product Owner adapt Product Backlog ordering and release expectations. The Increment does not become Done because stakeholders approve it; it is Done when it meets the Definition of Done.
The closest trap is treating the review as a release authorization gate, but Scrum uses empiricism, not stakeholder approval gates, to guide adaptation.
The Sprint Review is for inspecting the outcome and adapting future work, not for obtaining formal stakeholder sign-off.
Use the PSPO I Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Use the full PM Mastery practice page above for the latest review links and practice route.