Free PSPO II Practice Exam: Advanced Product Ownership
Try 40 original single-select PSPO II practice questions with answers and explanations, then review advanced Product Owner decisions in PM Mastery.
A 40-question practice run
Allow 60 minutes for this fixed set, then review the explanations. The questions are original PM Mastery practice, not official Scrum.org questions, copied live-exam content or exam dumps.
The set matches the official question count and time allowance. Its single-select format and ordinary right-or-wrong scoring do not reproduce the official Multiple Answer questions or partial credit. Treat it as a practice companion and pacing exercise, not an exact assessment simulation.
| Practice area | Questions in this set |
|---|---|
| Understanding and Applying the Scrum Framework | 8 |
| Managing Products with Agility | 20 |
| Evolving the Agile Organization | 12 |
This 20/50/30 distribution is editorial. Scrum.org does not publish these percentages as exam weights.
Before opening the answers
Choose an answer from the facts in the case. Note whether you were confident, uncertain or recalling a familiar question. At about 15, 30 and 45 minutes, check that you have reached questions 10, 20 and 30 without sacrificing careful reading. Adjust your pace; these checkpoints are practice aids.
Questions 1-25
Question 1
Topic: Evolving the Agile Organization
An investment committee must decide whether to release the remaining annual funding for three separate products or extend their limited validation funding. Each product has its own Product Owner, accountable for maximizing its value. The committee requests one consolidated revenue forecast, with each product’s assumptions and accountable Product Owner remaining visible.
Finance forecast: These are 80% forecast intervals for incremental revenue during the next 12 months. Amounts are in millions of dollars.
| Product | Revenue interval |
|---|---|
| Staff scheduling | 1-3 |
| Expense management | 2-4 |
| Inventory planning | 3-5 |
Shared assumption: Every interval assumes that the same distributor agreement is signed. It is still being negotiated, and there is no alternative customer channel within the forecast period. Without the agreement, all three products earn $0. Neither the probability of securing the agreement nor joint revenue uncertainty has been estimated.
Which consolidated forecast is best supported for the funding decision?
- A. Report $6-12 million as a conditional planning range alongside a $0 no-agreement scenario, with portfolio confidence still unquantified.
- B. Report $9 million as expected portfolio revenue, calculating it by summing the midpoints of the three product forecasts.
- C. Report $6-12 million as an 80% portfolio forecast interval, carrying forward the confidence level of the three product forecasts.
- D. Report $6 million as a conservative portfolio revenue floor, calculating it by summing the lower bounds of the product forecasts.
Best answer: A
Portfolio aggregation changes the reporting level, not the underlying uncertainty or Product Owner accountability. Adding the interval endpoints produces a $6-12 million conditional planning range. It does not establish an 80% forecast for total revenue: joint revenue outcomes are unknown, and every product depends on the same unresolved agreement. The $0 no-agreement scenario must remain visible, with its probability unquantified.
A consolidated report should keep each product’s assumptions, evidence and accountable Product Owner traceable. This lets the committee distinguish potential revenue from confidence in realizing it when choosing between further validation and a larger commitment. The committee remains responsible for portfolio funding decisions; Product Owners retain accountability for maximizing their respective products’ value.
Answer choices explained:
A — Correct: The conditional sum can inform planning, while the zero-revenue scenario exposes the common dependency without inventing a portfolio probability.
B — Incorrect: Interval midpoints are not necessarily expected values, and this calculation does not incorporate the unestimated probability of securing distributor access.
C — Incorrect: Individual 80% intervals do not establish an 80% interval for their sum, and all three estimates exclude the unresolved distributor-access risk.
D — Incorrect: The lower bounds are conditional forecast endpoints, not guaranteed minima; the shared agreement could fail and leave total revenue at $0.
Question 2
Topic: Managing Products with Agility
Paying customers of a reporting product experience recurring processing interruptions. The Product Owner can fund only one of two investments during the next 12 months. Each requires $120,000 upfront and competes for the same team capacity.
Investment forecasts:
- Reliability redesign: Adds no new functionality and finishes at the end of month 4. Representative trials support a 75% probability of reducing service-credit and support costs by $40,000 per month during months 5–12, and a 25% probability of no savings.
- Paid feature: Begins earning contribution in month 2. Its probability-weighted expected contribution is $20,000 per month during months 2–12.
All benefits are incremental to continuing the current product, net of ongoing operating costs, and exclude the upfront investment.
The agreed criterion is the greatest expected net contribution over these 12 months. Ignore discounting and economic effects not listed.
Which assessment best supports the funding decision?
- A. Prioritize reliability: expected 12-month net contribution is $120,000, versus $100,000 for the feature.
- B. Prioritize reliability: expected 12-month net contribution is $200,000, versus $100,000 for the feature.
- C. Prioritize the feature: expected 12-month net contribution is $100,000, versus $20,000 for reliability.
- D. Treat both investments as economically equivalent: expected 12-month net contribution is $120,000 for each.
Best answer: A
Reliability can create product value through fewer customer disruptions and lower recurring costs without adding functionality. Its economic assessment should reflect benefit timing, uncertainty, and competing uses of capacity.
The redesign offers eight months of potential savings. Probability-weighted savings are 75% of $320,000, or $240,000. After the $120,000 investment, expected net contribution is $120,000. The feature produces eleven months of expected contribution totaling $220,000, leaving $100,000 after investment.
Reliability therefore has a $20,000 expected advantage under the agreed criterion. The feature’s return is the opportunity-cost benchmark, not an additional expense to subtract before comparing the investments again. This forecast does not guarantee success: after deployment, inspect actual customer disruption and cost reductions at comparable usage, rather than treating completion of the redesign as proof of value.
Answer choices explained:
A — Correct: Eight months of probability-weighted savings total $240,000; subtracting the investment leaves $120,000, exceeding the feature’s expected $100,000 net contribution.
B — Incorrect: The $200,000 figure uses successful-case savings and ignores the 25% probability that the redesign produces no savings.
C — Incorrect: The $20,000 figure is reliability’s advantage after subtracting the feature’s net return; comparing that advantage with the feature again double-counts opportunity cost.
D — Incorrect: The feature earns contribution for eleven months, not twelve, producing $220,000 before the investment and $100,000 afterward.
Question 3
Topic: Managing Products with Agility
A financial-management product has this vision:
Help independent tradespeople keep their businesses financially resilient without becoming finance specialists.
The current Product Goal, giving users a consolidated view of bank and invoice records, has been fulfilled. An early roadmap emphasized advanced forecasting. Funding is available for one more quarter before expansion is considered.
Evidence from existing users:
- Bank and invoice records link most cash-shortfall weeks to customer invoices remaining unpaid after their due dates.
- A forecasting pilot improved prediction accuracy and users’ confidence, but cash-shortfall frequency did not improve.
- A small, manually operated invoice-follow-up trial was associated with earlier payments and fewer cash-shortfall weeks, without additional owner effort.
- Some users request easier financial reporting. A lending partner offers faster credit at market rates. Neither opportunity has been tested for its effect on financial resilience.
Which proposed next Product Goal offers the strongest supported contribution to the vision for the current target users?
- A. Enable existing users to bridge cash-shortfall weeks more reliably through faster access to credit at market rates.
- B. Enable existing users to reduce cash-shortfall weeks by collecting invoice payments closer to their due dates.
- C. Enable existing users to anticipate cash-shortfall weeks earlier through more accurate and longer-range financial forecasts.
- D. Enable existing users to spend less time handling financial records through simpler reconciliation and financial reporting.
Best answer: B
A product vision expresses an enduring purpose; a Product Goal describes a nearer-term future state that advances it. The forecasting roadmap represents an assumed route to financial resilience, not the vision itself.
Late payments are the strongest evidenced obstacle, and the follow-up trial suggests that earlier collection could reduce shortfalls without transferring more work to owners. A goal focused on this outcome preserves the product’s purpose while allowing the solution approach to change. It does not require committing to a particular reminder system, dashboard, or automation feature.
The small trial does not establish causation or lasting benefit. Further work should test whether the improvement persists and whether owner effort remains manageable. The Product Goal supplies direction for that work while Product Backlog content evolves through learning.
Answer choices explained:
A — Incorrect: Faster credit could cover payment gaps, but the partner’s offer does not demonstrate an improvement in users’ financial resilience.
B — Correct: Late payments are the main observed source of shortfalls, and the follow-up trial provides promising evidence of improvement without additional owner effort.
C — Incorrect: Forecast accuracy and confidence have already improved without fewer shortfalls, so extending forecasting lacks the strongest evidence of progress toward financial resilience.
D — Incorrect: Easier reporting could reduce administrative burden, but its effect on the segment’s principal financial-resilience problem has not been tested.
Question 4
Topic: Understanding and Applying the Scrum Framework
A Product Owner is considering a revised setup journey for a small-business invoicing product. A voluntary pilot with 24 experienced customers showed lower abandonment, but typical new customers are less experienced.
Decision facts:
- Setup abandonment represents an estimated $12,000 per week in forgone contribution. How much the revision could recover is unknown.
- Either randomized test costs $8,000, fits existing capacity, and meets customer-service commitments. The journey can be switched back within one day.
- A representative randomized test enrolling 30% of new customers is expected to provide decision-useful outcome evidence in four weeks. Enrolling 10% would require twelve weeks for comparable evidence.
- Broader rollout requires a $240,000 non-cancellable annual supplier contract.
- A broader customer preference study will report in eight weeks.
The priority is timely learning about activation outcomes while limiting irreversible financial exposure. Which next step is best supported?
- A. Run the 30% test now, then use its four-week results to decide on the annual supplier contract.
- B. Wait for the customer study, then run the 30% test before deciding on the annual supplier contract.
- C. Purchase the annual supplier contract now, roll out broadly, and reassess the journey after four weeks of outcome data.
- D. Run the 10% test now, then use its twelve-week results to decide on the annual supplier contract.
Best answer: A
Empirical decisions should match the evidence required to the consequences and reversibility of the action. The pilot supports further investigation, but its experienced volunteers do not establish benefit for typical customers.
The 30% randomized test is a reversible adaptation that can produce representative outcome evidence promptly, within existing capacity and customer-service commitments. That evidence can inform the much less reversible supplier investment.
Seeking more information also has a cost: it delays learning and may prolong recoverable abandonment. The $12,000 weekly estimate represents an opportunity at risk, not a guaranteed benefit from the revision. Acting now therefore means testing the hypothesis, not assuming it is true or committing immediately to scale.
Answer choices explained:
A — Correct: This provides timely, representative outcome evidence within existing capacity while keeping the substantial annual commitment contingent on demonstrated benefit.
B — Incorrect: Additional preference data might refine the design, but waiting postpones direct outcome learning while the potential activation benefit remains untested.
C — Incorrect: The purchase commits $240,000 before benefit for typical customers is established; reversing the journey would not reverse that expenditure.
D — Incorrect: The smaller test reduces immediate customer exposure, but triples the expected learning time without reducing testing cost or addressing a stated service constraint.
Question 5
Topic: Evolving the Agile Organization
A business-to-business marketplace is considering another quarter of funding for customer onboarding. Its proposed goal is:
Launch bulk file upload, reusable order templates, and an order-status page by quarter-end.
The commercial concern is that newly registered businesses often fail to place a valid first order promptly.
Available evidence:
- Last quarter, 58% of new accounts placed a valid first order within seven days under routine support.
- In a bulk-upload pilot, 16 of 20 volunteer new accounts placed a valid first order within seven days. These volunteers also received specialist onboarding unavailable in routine service.
- Pilot task testing showed faster file uploads than with the existing process.
A staged rollout to new accounts under routine support is feasible.
Which goal-and-evidence pair would best support deciding whether the new functionality justifies further investment?
- A. Aim to reduce file-upload time by 30%; compare upload times between comparable new-account cohorts using the new functionality and the existing process.
- B. Aim to increase seven-day first-order completion from 58% to 70%; assess the functionality’s contribution by comparing assisted pilot volunteers with the historical routine-support cohort.
- C. Aim to release all three features and achieve adoption by 70% of new accounts; assess release completion and feature usage against those targets.
- D. Aim to increase seven-day first-order completion from 58% to 70%; compare completion between randomly assigned new-account cohorts with and without the functionality under routine support.
Best answer: D
A delivery-scope goal identifies what will exist, but does not establish the improvement that would make the investment worthwhile. Here, seven-day first-order completion connects the work to the commercial concern. Increasing it from 58% to 70% provides a testable target, not a guaranteed result.
Randomly assigned cohorts receiving the same routine support provide stronger evidence of the functionality’s contribution. The pilot’s encouraging completion rate cannot isolate that contribution because participants volunteered and received additional assistance.
Release progress remains useful for understanding delivery feasibility, while adoption and upload times help reveal usage and friction. These measures complement outcome evidence rather than replace it. An outcome goal allows the Product Owner to continue, reorder, or stop feature work as evidence develops.
Answer choices explained:
A — Incorrect: Faster uploading improves one task, but the investment concern is successful first-order completion, which may remain unchanged despite that improvement.
B — Incorrect: Volunteer selection and additional onboarding support prevent the pilot comparison from isolating the functionality’s contribution to first-order completion.
C — Incorrect: Release completion and adoption show delivery and use, but neither establishes whether more new accounts successfully place a first order.
D — Correct: This connects investment to a measurable customer outcome and tests the functionality under comparable conditions representative of normal service.
Question 6
Topic: Managing Products with Agility
A Product Owner is ordering the Product Backlog for an automated replenishment service. Technical feasibility is established, but repeat use at the proposed price remains uncertain. A $600,000 nonrefundable supplier commitment must be accepted or declined at the end of the next Sprint. Declining closes the opportunity for the 12-month planning horizon.
Finance currently forecasts $800,000 in service contribution before the supplier fee. A $30,000 paid trial, manually fulfilling orders for representative retailers, would finish before the commitment deadline. Finance forecasts these possible updates:
| Trial result | Probability | Expected service contribution |
|---|---|---|
| Favorable | 50% | $1,400,000 |
| Unfavorable | 50% | $200,000 |
These are conditional forecasts, not guaranteed revenues.
The Developers confirm that only one initiative can finish next Sprint, with no partial benefits. Stakeholders have also identified:
- Retention improvement: Adds $150,000 in contribution regardless of the supplier decision.
- Supplier integration: Reduces the supplier fee by $140,000 if the commitment is made.
- Onboarding automation: Adds $130,000 to expected service contribution if the commitment is made.
All amounts cover the same 12-month horizon. Contributions exclude the supplier fee and trial cost; other costs are included. The listed gains reflect completing the initiative next Sprint rather than later, with subsequent work unchanged.
Which initiative should the Product Owner order highest to maximize expected net contribution, using the information available at the commitment deadline?
- A. Order the paid trial highest.
- B. Order the retention improvement highest.
- C. Order the onboarding automation highest.
- D. Order the supplier integration highest.
Best answer: A
Earlier learning has economic value when it can change an investment decision before costs become irreversible. Without the trial, committing produces an expected net contribution of $200,000: the $800,000 forecast less the $600,000 fee.
After a favorable trial result, committing would produce $800,000 in expected net contribution. After an unfavorable result, committing would produce an expected loss of $400,000, so the economically preferable decision would be to decline.
With equally likely results, this conditional strategy produces $400,000 in expected contribution before the trial cost, or $370,000 afterward. The trial therefore improves expected contribution by $170,000 over committing without new evidence. That exceeds the largest immediate delivery benefit, the $150,000 retention improvement.
The trial does not guarantee success. Its priority follows from its ability to improve this consequential decision, not from a general rule that experimentation should always precede delivery.
Answer choices explained:
A — Correct: Committing after a favorable result and declining after an unfavorable result yields $370,000 expected net contribution after the trial cost.
B — Incorrect: Its $150,000 gain plus the $200,000 expected return from committing without trial totals $350,000, below the trial-led strategy’s $370,000.
C — Incorrect: Its $130,000 uplift raises expected net contribution from committing without trial to $330,000, below the trial-led strategy’s $370,000.
D — Incorrect: The $140,000 fee reduction raises expected net contribution from committing without trial to $340,000, below the trial-led strategy’s $370,000.
Question 7
Topic: Managing Products with Agility
A Product Owner is preparing a release forecast for finance, which will use it to decide whether to authorize nonrefundable launch spending.
Historical evidence:
- The same six Developers worked through 20 two-week Sprints with a stable workflow and Definition of Done.
- A simulation using their completed-item throughput estimated an 85% probability that the remaining 36 similarly sized Product Backlog items would be Done within six Sprints.
Changes effective next Sprint:
- Two Developers leave and two experienced replacements join. This combination of Developers has no delivery history together.
- Every remaining item must complete a new external compliance review before meeting the Definition of Done.
- The review group reports a mean turnaround of two weeks for another product. Its turnaround variability and queue behavior for this product are unknown.
The remaining scope and item-size mix are unchanged. Finance asks whether 85% remains a supported likelihood for the release date.
Which forecasting response is best supported by this evidence?
- A. Extend the forecast by two weeks and retain 85%, using the external group’s mean turnaround as an adjustment to the historical model.
- B. Keep the six-Sprint, 85% forecast and disclose the changes as risks, using unchanged headcount and item-size mix to support comparability.
- C. Reduce modeled throughput to four-sixths of its historical level and add two weeks, then report 85% using the adjusted simulation.
- D. Publish conditional scenarios with explicit staffing and review assumptions, treating the earlier 85% result as a historical baseline rather than current confidence.
Best answer: D
A throughput-based forecast depends on historical observations being sufficiently representative of the delivery system being forecast. Unchanged headcount does not establish unchanged team performance. Mandatory external review also introduces a dependency, queues, and variability before work becomes Done.
The earlier forecast remains useful as a baseline, not as evidence that the changed system retains the same completion probability. Conditional scenarios can expose assumptions about onboarding, review capacity, waiting times, and overlapping work. These assumptions should be distinguished from observed evidence.
Adding another product’s mean review time does not preserve an 85% completion probability: an average does not describe the variability or queue interactions affecting the release. As the changed system operates, inspect end-to-end completion data and review delays, then update the forecast and its stated uncertainty.
Answer choices explained:
A — Incorrect: A mean turnaround from another product does not establish the delay distribution for this release or account for the changed team’s performance.
B — Incorrect: Equal headcount and comparable items do not establish comparable throughput after staffing and workflow changes; disclosing risks does not substantiate the retained probability.
C — Incorrect: Scaling throughput by the continuing Developers’ share and adding a fixed review delay introduces unsupported assumptions rather than establishing a defensible current probability.
D — Correct: The historical evidence remains informative, but its probability cannot be carried into the changed delivery system without examining the assumptions supporting that transfer.
Question 8
Topic: Managing Products with Agility
A payments product has a Product Goal of reducing customers’ transaction-reconciliation time. Two recently released changes based on customer feature requests have not reduced that time.
Current arrangement: All customer contact passes through the Product Owner. Developers receive interview summaries, and their follow-up questions typically wait eight days to be relayed. Customers say the summaries miss important workflow differences. Sales introduced this arrangement after a customer mistook a technical discussion for a delivery commitment.
Proposal: Customers and Developers want to examine their workflows together and publish their findings. Discussions would be explicitly exploratory, not delivery commitments. The Product Owner can attend some sessions but cannot attend every session.
Which working agreement best improves learning while preserving clear accountability for product decisions?
- A. Allow joint discussions as needed; the Product Owner uses their findings for product-priority decisions and remains accountable for effective Product Backlog management.
- B. Allow joint discussions as needed; participating customers and Developers have final authority over resulting priorities, which the Product Owner records in the Product Backlog.
- C. Use Product Owner-led joint discussions; the Product Owner attends each session and approves interpretations before Developers continue the conversation with customers.
- D. Use Sprint Reviews for the joint discussions; the Product Owner gathers and relays any customer clarifications needed between Reviews.
Best answer: A
Product Owner accountability does not require exclusive control of customer communication. Customers and Developers can learn directly from one another, uncover workflow differences, and test interpretations that interview summaries may obscure.
Here, delayed clarification and unchanged customer outcomes support improving discovery rather than simply implementing more requests. Exploratory discussions can produce evidence and possible solutions without becoming delivery commitments or automatically changing product priorities.
The Product Owner remains accountable for maximizing value and effective Product Backlog management. Others can contribute to or perform backlog-management work, but that accountability remains with one person. Making findings transparent helps the Product Owner make informed trade-offs without attending every conversation. The Sprint Review remains an important opportunity for inspection and adaptation, not the exclusive venue for stakeholder collaboration.
Answer choices explained:
A — Correct: Direct discovery reduces filtering and clarification delays while preserving the Product Owner’s accountability for turning evidence into product decisions.
B — Incorrect: Customers and Developers contribute evidence and proposals; participation does not give them final priority authority in place of the Product Owner.
C — Incorrect: Mandatory attendance and approval retain the communication bottleneck despite the Product Owner’s limited availability; accountability does not require mediating every exchange.
D — Incorrect: Sprint Reviews support stakeholder collaboration, but restricting direct discussions to that event preserves the delays affecting ongoing learning.
Question 9
Topic: Evolving the Agile Organization
A company is considering substantial investment in an automatic replenishment product for independent grocers. Its strategic customer outcome is to reduce store managers’ replenishment work by 40% within a year without increasing stockouts. The business case assumes managers will let routine orders reach suppliers without reviewing each one.
Evidence so far:
- Retrospective tests produced order quantities within the stores’ agreed tolerances.
- In usability sessions, managers successfully set spending limits and said they would try automatic ordering.
- The product has not yet submitted live supplier orders.
A working prototype can support four weekly ordering cycles in stores representative of the target segment. Spending limits and order overrides remain in place. The Product Owner must then recommend whether to fund broader development.
Which immediate tactical goal would provide the strongest evidence about the uncertain assumption in the business case?
- A. Determine whether stockouts remain at baseline over four weekly cycles when automatic submission is required by the pilot protocol.
- B. Determine whether managers reduce replenishment work over four weekly cycles when they review and approve every system-recommended order.
- C. Determine whether managers commit to using automatic submission next month after four weekly sessions comparing simulated orders with their actual orders.
- D. Determine whether managers voluntarily delegate routine ordering over four weekly cycles and reduce their total replenishment work.
Best answer: D
Immediate tactical goals can reduce uncertainty rather than deliver the entire strategic outcome. Here, technical plausibility and basic usability have some supporting evidence; voluntary delegation does not.
A short pilot should observe whether managers actually let routine orders proceed without individual review and whether their overall work begins to decrease. Measuring total work matters because managers might maintain parallel checks that undermine the expected benefit.
Favorable results would inform further investment, not prove that the 12-month outcome will be achieved. Persistence of the behavior, broader adoption, and longer-term stockout effects would still require inspection. The evidence can guide the next tactical goal or a change in the product approach.
Answer choices explained:
A — Incorrect: Stockout performance during required automation tests operational reliability rather than managers’ willingness to sustain voluntary delegation.
B — Incorrect: Time savings with per-order approval test assisted ordering, not whether managers will relinquish routine review as the business case assumes.
C — Incorrect: A commitment after simulations measures stated intent rather than repeated live delegation, which remains untested despite managers’ earlier expressions of interest.
D — Correct: Repeated voluntary delegation tests the missing behavioral assumption, while reduced total work checks early progress toward the intended customer outcome.
Question 10
Topic: Evolving the Agile Organization
Route Planner has a Done change with two usable modes. Assisted booking currently requires staff to reserve capacity through Capacity Manager, a separate product. Capacity Manager’s planned reservation API would remove that manual step, but its availability is forecast at 6 to 10 weeks.
Trial evidence: A representative trial maintained current booking accuracy in both modes. Net customer time savings compared with the existing workflow were:
| Mode | Saving per account per week |
|---|---|
| Recommendations-only | 20 minutes |
| Assisted booking | 50 minutes |
Rollout conditions:
- There are 600 eligible accounts with comparable booking volumes. Trial averages are expected to apply over the next four weeks.
- Modes can be enabled independently per account. Each account uses only one mode at a time.
- Existing staff can safely support assisted booking for at most 80 accounts throughout this period.
- Recommendations-only mode requires no additional staff and can support all 600 accounts.
- The Product Owners will coordinate readiness for API-backed booking separately; planning assumes the API will remain unavailable during these four weeks.
Which release approach best maximizes expected customer time saved over the next four weeks while maintaining current booking accuracy?
- A. Enable assisted booking for 80 accounts and recommendations-only mode for the other 520 accounts.
- B. Enable recommendations-only mode for all 600 accounts and defer assisted booking until the API is available.
- C. Retain the existing workflow for all 600 accounts and defer the change until the API is available.
- D. Enable assisted booking for 80 accounts and retain the existing workflow for the other 520 accounts.
Best answer: A
A cross-product dependency can constrain a particular mode or its scale without blocking the entire release. Both available modes are Done and have evidence of customer benefit at current booking accuracy. The missing API limits assisted-booking capacity, not recommendations-only delivery.
Assigning assisted booking to 80 accounts and recommendations-only mode to 520 accounts produces:
\[ \begin{gathered} 80 \times 50 + 520 \times 20 = 14{,}400\\ \text{ customer-minutes saved per week} \end{gathered} \]That is 57,600 customer-minutes over four weeks under the trial-based assumptions. This allocation uses all available capacity for the higher-benefit mode while preserving independent value for everyone else. The Product Owners can coordinate API readiness and subsequent expansion without imposing a synchronized release on capabilities that are already usable. Actual savings and booking accuracy should be inspected to validate the forecast.
Answer choices explained:
A — Correct: This uses the higher-benefit mode up to supported capacity while providing independent recommendation benefits to every remaining account.
B — Incorrect: This saves 48,000 customer-minutes over four weeks but leaves the additional benefit available through existing assisted-booking capacity unrealized.
C — Incorrect: Waiting sacrifices supported near-term benefits because the API dependency limits assisted-booking scale, not the usability of both available modes.
D — Incorrect: This saves 16,000 customer-minutes over four weeks but forgoes supported recommendation benefits for the other 520 accounts.
Question 11
Topic: Managing Products with Agility
A Product Owner for a subscription scheduling product has funding for only one improvement next quarter: richer reporting or simpler initial setup. The Product Goal is to increase first-year renewals. Reporting is ordered first because the team assumes missing reports are a major cause of non-renewal.
Over six weeks, the team conducts five customer interviews per week. Notes contain recurring requests for richer reports and complaints about setup. The Product Goal, written assumptions, and Product Backlog ordering remain unchanged. The funding proposal presents the interview count and recurring themes as evidence that discovery is effective.
Which assessment would best determine whether the interviews are improving this investment decision?
- A. Assess how the findings affect confidence that reporting improves renewals, using that evidence to determine whether to retain or change the current priority.
- B. Assess how well interview participants represent customer segments, using broad coverage and consistent themes as evidence that the current investment priority is justified.
- C. Assess how closely the current priority matches the most frequent customer requests, using recurring interview themes as evidence that the priority is justified.
- D. Assess how often the interviews changed the Product Goal or Product Backlog ordering, using the frequency of changes as evidence of better investment decisions.
Best answer: A
Customer research improves a product decision when it strengthens the evidence behind that decision, not simply when it produces notes or causes changes. Here, the investment rests on the assumption that richer reporting will improve first-year renewals. The Product Owner should examine whether the findings support that assumption, challenge it in favor of addressing setup, or leave the uncertainty unresolved.
Recurring requests can identify needs, but they do not by themselves establish why customers fail to renew. Interviews may need to be combined with product-use evidence, renewal behavior, or a bounded experiment. Keeping the Product Goal and ordering can be reasonable when evidence strengthens their basis. Interview volume, repeated themes, and the absence of changes do not independently establish whether discovery is improving the decision.
Answer choices explained:
A — Correct: This connects research to the assumption driving the investment; stronger supporting evidence could justify retaining the priority rather than changing it.
B — Incorrect: Representative participation improves research credibility, but coverage and consistent themes alone do not establish which improvement would affect renewals.
C — Incorrect: Recurring requests reveal expressed preferences, but do not establish whether reporting rather than simpler setup would improve first-year renewals.
D — Incorrect: Counting changes rewards movement rather than better judgment; research can improve a decision by corroborating its assumptions and supporting an unchanged priority.
Question 12
Topic: Understanding and Applying the Scrum Framework
A Scrum Team’s Product Goal is to reduce customers’ billing-resolution time without increasing manual support effort. The Product Owner is considering expanding a pilot to all customers.
At the Sprint Review, the Scrum Team’s only guests are executives authorized to approve spending. Affected customers and support staff are absent.
Evidence and discussion:
- The team demonstrates a Done Increment and presents pilot data showing faster resolution.
- The Product Owner has preliminary customer reports of confusing resolution messages and support records suggesting increased manual corrections. These are withheld from the review pending validation.
- The executives endorse funding the expansion based on the demonstration and presented results.
Which judgment is best supported about the review’s transparency as a basis for the expansion decision?
- A. The review provided an adequate basis because the sponsors had spending authority and inspected a Done Increment with favorable pilot results.
- B. The review provided an adequate basis because deferring unvalidated feedback preserved evidence quality while demonstrated functionality and measured improvements supported expansion.
- C. The review provided an inadequate basis because unresolved customer and support evidence relevant to the Product Goal was excluded from collective inspection.
- D. The review provided an inadequate basis because affected customers and support staff are required participants whenever expansion of their product is discussed.
Best answer: C
A Sprint Review enables joint inspection of product results and progress toward the Product Goal to inform future adaptations. Here, faster resolution is relevant, but increased manual corrections could undermine the goal’s support-effort condition. Customer reports may also challenge the interpretation of the favorable results. Their preliminary status should be transparent, allowing participants to consider validation or further learning before broad expansion.
Scrum does not mandate a fixed guest list or attendance by every affected group. Relevant stakeholder knowledge can contribute through direct participation or credible, inspectable evidence. The central problem is therefore not automatically the absence of customers and support staff, but the exclusion of their relevant evidence. Funding endorsement does not compensate for that gap, and the Sprint Review is not an approval gate.
Answer choices explained:
A — Incorrect: Spending authority and favorable results do not establish progress toward both parts of the Product Goal when relevant contrary signals remain unseen.
B — Incorrect: Preliminary evidence can be inspected with explicit limitations; withholding these goal-relevant signals conceals uncertainty rather than resolving it before expansion.
C — Correct: The omitted signals concern customer experience and manual support effort, preventing participants from weighing material uncertainty alongside the favorable pilot results.
D — Incorrect: Scrum does not prescribe these groups as mandatory attendees; their absence alone does not determine whether relevant evidence can be inspected and used.
Question 13
Topic: Evolving the Agile Organization
Maya is the Product Owner for a merchant onboarding product. The Scrum Team’s Product Goal is to help more new merchants complete activation without support.
Current governance:
- The board sets a quarterly funding limit and mandatory regulatory controls.
- Sales, operations, and portfolio committees routinely override Maya’s Product Backlog ordering. Changing a committee’s instruction requires its approval.
- These interventions have postponed experiments investigating activation failures. Both the experiments and committee requests fit the Product Goal and existing boundaries; their relative value remains untested.
The board wants to retain investment and regulatory oversight while making Maya’s accountability for product value workable. Which governance change most directly supports that aim?
- A. Reserve a protected experiment allocation that Maya can order independently, with committees retaining ordering authority over the rest of the Product Backlog.
- B. Keep committee ordering authority and require an executive sponsor to resolve disputed priorities after hearing Maya’s evidence about expected product value.
- C. Consolidate the committees into one product council that approves Product Backlog ordering, with Maya preparing recommendations supported by product evidence.
- D. Make Maya’s Product Backlog ordering decisions authoritative within the existing boundaries, with committees providing advisory input into product priorities.
Best answer: D
Product Owner accountability requires the organization to respect that person’s decisions, including Product Backlog ordering. A role title does not provide usable authority when committees routinely replace those decisions.
Governance and empowerment can coexist. The board can retain funding limits and mandatory regulatory controls, while committees contribute expertise, challenge assumptions, and inspect outcomes. Within those boundaries, Maya needs authority to weigh value, risk, and learning across the whole Product Backlog.
This does not establish that Maya’s experiments are more valuable than the committees’ requests. Their relative value remains uncertain. It establishes a single accountable decision-maker who can act on available evidence, inspect results, and adapt rather than merely administer decisions made elsewhere.
Answer choices explained:
A — Incorrect: Authority over an experiment allocation provides partial empowerment while leaving product-wide ordering trade-offs under committee control.
B — Incorrect: Executive arbitration can resolve disputes, but Maya would remain dependent on another authority to make her ordering decisions effective.
C — Incorrect: A single approval council reduces conflicting instructions but still places final ordering authority outside the Product Owner.
D — Correct: This gives the accountable Product Owner usable ordering authority while preserving the board’s investment and regulatory boundaries.
Question 14
Topic: Understanding and Applying the Scrum Framework
An invoicing product’s Product Goal is to help new small businesses send their first invoice without support. Onboarding support costs are rising, so the immediate priority is a usable improvement for these customers in the next two-week Sprint.
Sprint Planning evidence:
- The Product Owner initially ordered automatic accounting-data import first to simplify onboarding.
- Customer observations show that many users abandon the existing manual-entry flow because they cannot understand how to correct validation errors.
- Developers report undocumented behavior in the import provider’s interface. They cannot yet forecast a usable import capability within the Sprint.
- Developers consider an independent improvement to the manual-entry flow feasible within the Sprint.
Which Product Owner contribution best supports a valuable and feasible Sprint?
- A. Propose improving manual-entry completion and set the error-guidance items as mandatory Sprint scope; let Developers determine implementation tasks, technical approach, and work allocation.
- B. Propose automatic import as the Sprint Goal and retain its first position; let Developers plan implementation and revise selected scope as provider behavior becomes clearer.
- C. Propose resolving import feasibility as the Sprint Goal and prioritize the investigation; let Developers plan that work and add manual-entry improvements if capacity remains.
- D. Propose a Sprint Goal of enabling unaided first invoices through manual entry; discuss ordering and scope while Developers select work and create their delivery plan.
Best answer: D
Sprint Planning combines why the Sprint is valuable, what can be accomplished, and how the work will be done. The Product Owner contributes product purpose, customer evidence, and Product Backlog ordering. Here, unclear validation errors are an observed obstacle, and Developers identify a feasible path to improving that experience independently of the uncertain integration.
The Scrum Team can therefore collaborate on a focused Sprint Goal and reconsider ordering. Developers select Product Backlog items through discussion with the Product Owner and create the plan for delivering them. The Product Owner clarifies value and negotiates scope rather than imposing a forecast or assigning implementation tasks.
Technical investigation may still be included in the plan. Its potential value does not automatically justify displacing the stated immediate customer priority.
Answer choices explained:
A — Incorrect: The Product Owner can order items and clarify value, but cannot impose Sprint scope while leaving Developers responsible only for implementation.
B — Incorrect: Scope flexibility does not establish a credible import goal when Developers cannot yet forecast a usable import capability within the Sprint.
C — Incorrect: Making investigation the priority subordinates the immediate customer benefit despite evidence of a feasible, independent route to a usable improvement.
D — Correct: This connects customer evidence to a feasible goal while preserving Developers’ responsibility for selecting work through discussion and determining their implementation plan.
Question 15
Topic: Evolving the Agile Organization
A Product Owner is preparing a quarterly funding review for a product developed by two Scrum Teams. Leaders want more successful customer onboarding and faster testing of product improvements. They propose moving two Developers from Enablement to Journey based on these measures.
| Measure | Journey | Enablement |
|---|---|---|
| Prior-quarter velocity | 40 | 24 |
| Current-quarter velocity | 60 | 24 |
| Current planned utilization | 95% | 70% |
Velocity is measured in story points per Sprint. Planned utilization is the percentage of available developer time allocated when planning a Sprint.
Context:
- Both teams have six Developers, but their story-point reference scales differ.
- Journey develops onboarding flows. Enablement maintains shared delivery capabilities and handles unpredictable production incidents, deliberately reserving capacity for them.
- Both teams contribute to the same Product Goal and integrated releases.
- Onboarding completion increased from 61% to 68% across comparable customer cohorts during the quarter.
- Changes ready for customer testing wait a median of nine days for a centrally controlled release approval that neither team can grant.
Which use of the measures provides the strongest basis for the funding review?
- A. Use velocity growth against each team’s own baseline as investment evidence, with planned utilization indicating which team offers the stronger funding opportunity.
- B. Use shared onboarding outcomes and release delays as investment evidence, with velocity and planned utilization informing investigation of each team’s delivery context.
- C. Use incident-adjusted story points per Developer as investment evidence, with the shared onboarding improvement validating the ranking of teams’ value contributions.
- D. Use Journey’s onboarding gains and Enablement’s release delays as investment evidence, with those results indicating the teams’ relative contributions to product value.
Best answer: B
Organizational measures should reveal customer results and constraints on adaptation, rather than turn local estimates into a team ranking. The onboarding improvement is product-level outcome evidence, but it does not isolate either team’s contribution. The approval wait exposes a system-level delay in obtaining customer feedback.
Velocity can support a team’s forecasting when its context is sufficiently stable. Dividing points by headcount or comparing percentage growth does not convert them into comparable measures of value. Planned utilization shows advance allocation, not value delivered or genuinely spare capacity. Enablement’s deliberate reserve supports its response to unpredictable incidents.
The funding review should examine customer outcomes and constraints on delivering and learning. Local measures can help investigate those constraints, but the figures do not establish that moving Developers would improve the product’s results.
Answer choices explained:
A — Incorrect: Growth against a team’s own baseline describes a local output trend; neither that growth nor planned utilization establishes comparative investment returns.
B — Correct: The customer result and approval delay inform product investment; the local measures do not establish that transferring Developers would improve either.
C — Incorrect: Adjusting for incidents and headcount does not make independently calibrated story points comparable, and a shared outcome cannot validate the resulting team ranking.
D — Incorrect: The onboarding result followed integrated releases, while approval is centrally controlled; attributing these measures to individual teams misrepresents the evidence.
Question 16
Topic: Managing Products with Agility
A SaaS Product Owner has one team that can develop only one of three opportunities during the next 12 months. Opportunities cannot be combined within that window. The decision criterion is to maximize expected net contribution over those 12 months.
Forecasts: Contribution occurs only if customer adoption is sufficient; otherwise contribution is $0. Development costs are incurred either way. Use these agreed planning estimates:
| Opportunity | Contribution if adopted | Adoption probability | Development cost |
|---|---|---|---|
| Analytics | $1,200,000 | 40% | $300,000 |
| Renewals | $700,000 | 75% | $200,000 |
| Onboarding | $450,000 | 90% | $100,000 |
Available pilot: Before selecting development work, the team could run a six-week analytics pilot costing an additional $60,000.
- Positive and negative results are equally likely.
- A positive result raises the analytics adoption estimate to 70%; a negative result lowers it to 10%.
- Neither result changes the adoption estimates for renewals or onboarding.
- After the pilot, any opportunity remains feasible, but its contribution if adopted would be 10% lower because of the delay. Development costs remain unchanged.
- No other pre-development experiments are available.
Which use of the team’s capacity is best supported by these forecasts?
- A. Begin development of the onboarding opportunity now.
- B. Begin development of the renewals opportunity now.
- C. Run the analytics pilot before selecting an opportunity for development.
- D. Begin development of the analytics opportunity now.
Best answer: B
Expected net contribution weights adoption-dependent contribution by its probability, then subtracts costs incurred regardless of adoption. For renewals, the calculation in dollars is \(0.75 \times 700{,}000 - 200{,}000 = 325{,}000\). Neither the largest headline benefit nor the highest adoption probability independently determines the strongest investment.
The pilot provides useful information, but its cost and delay reduce its economic value. After a positive result, analytics would be the best development investment, yielding expected net contribution of $456,000. After a negative result, renewals would be best, yielding $272,500. These amounts include the 10% reduction in contribution and unchanged development costs.
With equally likely results, the pilot’s maximum expected net contribution in dollars is:
\[ \begin{aligned} &0.5 \times 456{,}000\\ &\quad + 0.5 \times 272{,}500\\ &\quad - 60{,}000 = 304{,}250 \end{aligned} \]Starting renewals now therefore maximizes expected net contribution under the stated estimates. The estimates support an investment decision, not a guarantee of realized customer demand or value.
Answer choices explained:
A — Incorrect: Onboarding’s higher adoption probability yields expected net contribution of $305,000 after development costs, below the $325,000 expected from renewals.
B — Correct: Renewals yields $325,000 in expected net contribution, calculated as 75% of $700,000 less $200,000, exceeding every available alternative.
C — Incorrect: Even with optimal follow-up decisions, the pilot yields expected net contribution of $304,250 after its cost and delayed benefits, below starting renewals.
D — Incorrect: Analytics has expected contribution of $480,000 before its $300,000 development cost, leaving $180,000, below the expected return from renewals.
Question 17
Topic: Managing Products with Agility
An online retailer is building self-service refunds for damaged deliveries. Its Product Backlog separates customer screens, a new claims-data service, and an automated assessment engine into large items. None enables a customer to complete the refund journey on its own.
The Product Owner must recommend whether to expand investment. The priority is early evidence that customers can submit adequate damage evidence and obtain refunds without contacting support.
Known facts:
- Existing reviewers assess claims and issue refunds through an audited operations system. They have capacity for a small live pilot.
- A secure connector to that system is required for any live flow. Developers can deliver it independently of automated assessment.
- Developers estimate that automated assessment would delay a live pilot by at least three Sprints compared with using existing reviewers.
- A high-volume product category exhibits submission difficulties representative of other categories.
Every proposed release would include the connector and meet the unchanged Definition of Done, including secure evidence handling and refund auditability.
Which initial release scope best supports the Product Owner’s funding decision?
- A. A customer-facing claim-to-refund flow for the high-volume category, with existing reviewers assessing claims and issuing refunds.
- B. A customer-facing evidence-submission flow across all categories, with customers calling support to complete each refund.
- C. A support-agent claim-to-refund flow across all categories, using the new claims-data service and automated assessment engine.
- D. A customer-facing claim-to-refund flow across all categories, using the new claims-data service and automated assessment engine.
Best answer: A
Usable slices should span a customer outcome rather than follow technical layers. Here, a complete flow for a representative category can combine new submission functionality with the existing review and refund service. Customers can attempt the whole journey, allowing observation of evidence quality, support contacts, and completed refunds.
The secure connector remains necessary, and the Definition of Done is unchanged. Using human reviewers does not make the Increment incomplete when automated assessment is outside its scope and the intended service is usable. It postpones a larger technical investment while testing the customer-facing uncertainty. Results from a limited pilot can inform expansion, but they do not yet demonstrate that manual processing will scale or that automation will be economically justified.
Answer choices explained:
A — Correct: The representative category supports a complete refund journey, while existing reviewers enable customer-behavior evidence before investment in automated assessment.
B — Incorrect: Evidence submission covers only part of the customer outcome; a mandatory support call prevents testing whether refunds can be obtained without contacting support.
C — Incorrect: Automating agent work may improve internal efficiency, but it does not test customers’ ability to complete self-service claims and delays that evidence.
D — Incorrect: Full automation provides an end-to-end customer flow, but adds at least three Sprints before the customer behavior central to the funding decision can be observed.
Question 18
Topic: Managing Products with Agility
A Product Owner is reviewing further investment in a scheduling product. Renewal rates have fallen from 72% to 54% across comparable annual customer cohorts. The executive sponsor says:
“We have spent $4 million, and our leadership team’s credibility is attached to this product.”
The investment committee must select one of four mutually exclusive proposals. Its agreed criterion is the highest expected incremental net cash contribution over the next 18 months. Finance provides comparable forecasts based on current evidence:
| Proposal | Future costs | Expected cash inflows |
|---|---|---|
| Recovery roadmap | $300,000 | $390,000 |
| Niche repositioning | $180,000 | $300,000 |
| Adjacent product | $250,000 | $420,000 |
The remaining proposal is a new-segment experiment:
- The experiment costs $40,000 and has a 25% probability of meeting its validation threshold.
- Meeting the threshold triggers $160,000 of follow-on investment, with expected cash inflows of $600,000 within the same horizon.
- Missing the threshold triggers no further investment or incremental cash inflows.
All amounts are incremental to the same baseline of honoring existing customer commitments and include relevant transition costs. No additional financial consequences have been identified for any proposal.
Which funding recommendation is best supported?
- A. Allocate the available investment to the scheduling product’s niche repositioning.
- B. Allocate the available investment to developing the adjacent product.
- C. Allocate the available investment to the scheduling product’s recovery roadmap.
- D. Allocate the available investment to the new-segment experiment and contingent follow-on.
Best answer: B
Responsible investment compares future value and opportunity costs. The $4 million already spent is a sunk cost: further funding cannot change that expenditure.
Subtracting future costs from expected inflows gives $90,000 for recovery, $120,000 for niche repositioning, and $170,000 for the adjacent product. The experiment’s expected net contribution, in dollars, is:
\[ \begin{aligned} &0.25 \times (600{,}000 - 160{,}000)\\ &\quad - 40{,}000 = 70{,}000 \end{aligned} \]The adjacent product therefore best satisfies the committee’s criterion. Positive expected returns from the existing product do not establish that reinvestment is the best use of limited resources. Likewise, a bounded experiment is not automatically preferable to another investment.
Make the forecasts, assumptions, and resulting trade-off transparent. Redirecting funding updates a decision using current evidence; it need not imply that earlier decisions were unreasonable or that their sponsors deserve blame. Expected values remain forecasts, so subsequent customer and financial outcomes still require inspection.
Answer choices explained:
A — Incorrect: Its expected net contribution is $120,000, so continued investment could create value while forgoing a larger expected contribution elsewhere.
B — Correct: Its expected net contribution is $170,000, the highest among the mutually exclusive proposals; past spending does not change that comparison.
C — Incorrect: Its $90,000 expected net contribution is positive, but lower than the $170,000 available from the adjacent product.
D — Incorrect: After the experiment cost and probability-weighted follow-on returns, its expected net contribution is $70,000, below the adjacent product’s $170,000.
Question 19
Topic: Managing Products with Agility
A software product helps independent maintenance firms complete repairs by the promised date. Operations managers buy it; dispatchers and technicians use it. Its current Product Goal is to improve on-time completion for existing customers.
Three proposed extensions have positive three-year contribution forecasts after estimated costs. Lending has the highest forecast contribution, but willingness to pay and operating costs remain unvalidated for all three.
- Parts ordering: Builds on existing parts-availability integrations but adds distributor contracts and transaction support. At 12 representative customer firms, late repairs numbered 190 of 1,000 during a six-week pilot, compared with 280 of 1,000 in the preceding six weeks. There was no control group.
- Invoice lending: Owners of existing customer firms request financing for emergency parts purchases. This would require underwriting capabilities and lender relationships. Its effect on repair completion has not been tested.
- Technician certification marketplace: Existing customers report skill shortages, and training providers express interest in paying for access to these firms. This would require credential verification and relationships with training providers. Its effect on repair completion has not been tested.
The team can validate one extension next quarter, delaying planned scheduling improvements, or investigate those scheduling improvements instead. Their effect on repair completion is also untested.
The investment priority is evidence-supported progress toward the current Product Goal while avoiding a persistent diversion into a different business. Which product-boundary recommendation is best supported?
- A. Explore lending as an extension of this product, keeping parts ordering and certification outside its boundary for now.
- B. Explore certification as an extension of this product, keeping parts ordering and lending outside its boundary for now.
- C. Explore parts ordering as an extension of this product, keeping lending and certification outside its boundary for now.
- D. Explore scheduling improvements within this product, keeping parts ordering, lending and certification outside its boundary for now.
Best answer: C
A coherent product boundary follows a customer problem and value hypothesis, not every profitable opportunity involving the same customers. Parts ordering has the strongest available connection to the current Product Goal: a preliminary improvement in repair completion and an existing integration base.
The pilot does not establish causation. Differences in repair mix or other conditions could explain the change. The next investment should therefore validate the effect using comparable cohorts, alongside willingness to pay and the costs of distributor support.
Lending and certification may be worthwhile businesses without belonging inside this product. Their new capabilities and relationships create continuing opportunity costs, not merely initial development costs. Keeping them outside the boundary for now preserves focus without rejecting their potential portfolio value.
Answer choices explained:
A — Incorrect: Lending has attractive projected returns and interested customers, but its contribution to repair completion is untested and requires a distinct financial-services capability.
B — Incorrect: Reported skill shortages suggest relevance, but training-provider interest does not establish improved repair completion and introduces a different customer relationship and capability.
C — Correct: Parts ordering has preliminary outcome evidence relevant to the Product Goal and builds on existing integrations, supporting further validation rather than immediate full expansion.
D — Incorrect: Scheduling remains consistent with the product’s purpose, but its untested outcome effect provides less support for the next investigation than the parts-ordering pilot.
Question 20
Topic: Evolving the Agile Organization
A Product Owner for accounting software must decide whether to fund further extensions to a bank-reconciliation capability. The value hypothesis is that it will reduce the total time small-business bookkeepers spend on monthly reconciliation, including corrections and work outside the product.
Evidence from three Sprints:
- The team released Done Increments adding suggested transaction matches, reusable matching rules, and an exception dashboard.
- Active use increased after each release.
- Bookkeepers requested refinements at each Sprint Review, and the Product Owner adapted Product Backlog ordering in response.
- The collected evidence covers feature use and requested functionality. No measurements or customer reports of changes in total reconciliation time have been collected.
Which interpretation of this evidence should guide the Product Owner’s assessment of whether the value hypothesis has been tested?
- A. The value hypothesis is contradicted, since three releases without reported time savings demonstrate that the capability has not reduced customers’ total reconciliation time.
- B. The value hypothesis is supported, since increasing use across the releases demonstrates that customers obtain the expected reduction in reconciliation time.
- C. The value hypothesis remains untested, since the evidence concerns feature use and requested refinements rather than changes in customers’ total reconciliation time.
- D. The value hypothesis is supported, since repeated customer feedback and backlog adaptations demonstrate empirical learning about the expected reduction in reconciliation time.
Best answer: C
Incremental delivery creates opportunities to learn, but each Increment is not automatically a test of customer value. A customer-outcome learning cycle requires inspecting evidence relevant to the hypothesis and adapting in response.
Here, the team has learned about adoption and customer preferences. That learning can inform product decisions, but it does not establish whether monthly reconciliation takes less time. Product use could increase while total effort remains unchanged or shifts to corrections and offline work.
A bounded next experiment could observe representative bookkeepers completing reconciliation and compare total effort with a relevant baseline. The result could support, challenge, or refine the hypothesis and inform further investment. The existing evidence neither confirms nor refutes the expected time saving.
Answer choices explained:
A — Incorrect: An unobserved result is not a negative result; no outcome evidence was collected to establish that reconciliation time remained unchanged.
B — Incorrect: Increased use establishes adoption, not time savings; customers could use the capability while still spending as long on reconciliation overall.
C — Correct: Usage and refinement feedback inform adoption and design decisions, but neither tests the hypothesized reduction in total customer effort.
D — Incorrect: Feedback-driven adaptations can improve functionality without testing its effect on reconciliation time; adapting the Product Backlog does not itself validate the outcome hypothesis.
Question 21
Topic: Evolving the Agile Organization
A subscription product’s leadership is considering expanding its existing growth strategy. The Product Owner must assess whether the evidence supports sustainable value over the next year.
Product evidence:
| Measure | Previous quarter | Latest quarter |
|---|---|---|
| Product revenue | $3,000,000 | $3,600,000 |
| Target customers reporting a high-priority unmet need | 45% | 45% |
| Development time required for rework and production support | 25% | 55% |
| Median decision-to-customer-test time | 3 weeks | 9 weeks |
Team size and measurement definitions are unchanged. Customer samples represent the same target market, and test-time data covers comparable small experiments. No experiment has established whether addressing the reported unmet need would cause customers to adopt or pay more.
Which interpretation is best supported for the investment discussion?
- A. The trends suggest a validated growth opportunity: higher revenue demonstrates demand for addressing unmet needs, with innovation capacity and delivery speed remaining execution constraints.
- B. The trends suggest a sustainability risk: higher revenue coexists with potential unmet value and a weakening capacity to innovate and deliver.
- C. The trends suggest sustainable growth: higher revenue and persistent unmet need compensate for reduced innovation capacity and slower delivery.
- D. The trends suggest declining current value: increased support effort and slower delivery indicate that lower profitability outweighs the improvement in revenue.
Best answer: B
Evidence-Based Management’s four Key Value Areas should be interpreted together. Growing revenue is a positive Current Value signal, but it does not establish sustainable value by itself. The persistent unmet need indicates potential Unrealized Value; adoption and willingness to pay remain untested.
More development time required for rework and support signals pressure on Ability to Innovate. Longer elapsed time to put comparable experiments before customers signals worsening Time-to-Market and delayed learning.
Together, these measures show how current results can improve while the capacity to capture future opportunities weakens. Expansion should therefore remain an investment hypothesis, evaluated using evidence about both the opportunity and the product’s ability to respond, rather than justified by revenue growth alone.
Answer choices explained:
A — Incorrect: Revenue from the existing product does not validate willingness to adopt or pay for a solution to the reported unmet need.
B — Correct: The unmet need suggests possible future value, while rising support demands and longer test delays threaten the ability to discover and realize it.
C — Incorrect: The evidence provides no basis for treating revenue growth as compensation for weakened capabilities, and persistent unmet need does not establish monetizable demand.
D — Incorrect: Support effort and test delays reveal capability pressures, but without cost or margin evidence they do not establish falling profitability.
Question 22
Topic: Evolving the Agile Organization
The Product Goal for an invoicing service is to increase the proportion of new firms sending their first invoice within seven days. The Product Owner tests whether guided setup improves this outcome by reducing setup effort in both customer segments.
Trial: In each segment, 400 new firms were randomly split equally between existing and guided setup. Every firm was observed for the full seven days.
| Segment | Existing setup: first invoice sent | Guided setup: first invoice sent |
|---|---|---|
| Owner-run firms | 45% | 70% |
| Multi-approver firms | 40% | 41% |
Additional evidence:
- Median hands-on setup time fell from 24 to 12 minutes in both segments.
- At day seven, about 70% of multi-approver firms missing the outcome were awaiting a colleague’s approval.
- Interviews confirm that faster first invoicing remains important to both segments. Market analysis indicates similar revenue potential for each segment.
Funding covers one more experiment before broader investment. The next decision should preserve demonstrated outcome benefits and investigate the most consequential remaining uncertainty about first-invoice completion.
Which direction is best supported?
- A. Keep the first-invoice goal, retain guided setup for owner-run firms, and test whether improved approval handoffs increase completion in multi-approver firms.
- B. Replace the first-invoice goal with reduced setup effort, retain guided setup for both segments, and test whether further simplification reduces setup time.
- C. Narrow the first-invoice goal to owner-run firms, retain guided setup there, and test whether further simplification increases that segment’s completion.
- D. Keep the first-invoice goal, retain guided setup for both segments, and test whether further simplification increases completion in multi-approver firms.
Best answer: A
An experiment can support a solution for one segment while challenging its assumed mechanism for another. Guided setup substantially improved first-invoice completion among owner-run firms. For multi-approver firms, lower setup effort did not translate into a comparable improvement. This challenges the assumption that setup effort is their limiting factor, rather than showing that faster first invoicing is unimportant.
Retain the Product Goal and the demonstrated owner-run benefit. Use the next experiment to test whether improved approval handoffs increase seven-day first-invoice completion in multi-approver firms. Compare the revised handoffs with current practice using comparable customers and the same observation window. The waiting records make approval coordination a promising hypothesis, but they do not yet prove that changing it will improve the outcome.
Answer choices explained:
A — Correct: The results support preserving the owner-run benefit while testing the approval constraint suggested by multi-approver firms’ behavior.
B — Incorrect: Reduced effort is an intermediate result; improving it does not establish that the still-valued first-invoice outcome should be replaced.
C — Incorrect: Weak results in multi-approver firms challenge the proposed solution, not the segment’s comparable commercial opportunity or continuing need for faster first invoicing.
D — Incorrect: Further simplification is less supported than testing approval handoffs, since halving setup time produced little change in multi-approver firms’ first-invoice completion.
Question 23
Topic: Understanding and Applying the Scrum Framework
A payments Scrum Team has six days left in its Sprint. Its Sprint Goal is to enable small retailers to activate payments without support. A partner offers access to a new retailer segment through a pilot that must start in four days.
- The pilot requires an additional identity-verification path that supports the current Sprint Goal.
- The Product Owner judges the pilot more valuable than two selected onboarding refinements.
- Developers forecast that replacing those refinements would allow the pilot to be ready by the deadline while achieving the Sprint Goal.
The sales director tells the Product Owner:
Assign the pilot tasks to our two integration specialists and require daily progress reports from each Developer until launch.
Which response best addresses the deadline and the need for visibility while respecting Scrum accountabilities?
- A. Renegotiate Sprint scope with the Developers, ask the Scrum Master to allocate pilot tasks, and use consolidated daily individual reports to track readiness.
- B. Cancel the Sprint and propose a pilot-focused Sprint Goal, leave task allocation to the Developers, and agree on daily shared visibility of pilot readiness.
- C. Renegotiate Sprint scope with the Developers, temporarily assign the pilot tasks, and review daily individual reports to decide whether to reallocate work.
- D. Renegotiate Sprint scope with the Developers, leave task allocation to them, and agree on daily shared visibility of pilot readiness and Sprint Goal risks.
Best answer: D
Urgency changes the value and timing of work, not Scrum’s accountabilities. The Product Owner clarifies the opportunity, value trade-offs, and stakeholder information needs. Developers decide how to create the Increment and manage their Sprint Backlog, including how they organize their work.
The pilot supports the existing Sprint Goal, and Developers forecast that exchanging scope is feasible. The Product Owner and Developers can therefore renegotiate selected work rather than treating the original selection as fixed.
Daily visibility can come from agreed updates on readiness, risks, and forecasts. Requesting information is not itself a violation of self-management; using individual reports as a mechanism for directing assignments is the problem. The Daily Scrum also need not become a status-reporting meeting for the Product Owner.
Answer choices explained:
A — Incorrect: The Scrum Master supports self-management; transferring task-allocation authority to that role does not preserve the Developers’ authority over organizing their work.
B — Incorrect: The pilot supports the existing Sprint Goal, so the opportunity has not made that goal obsolete and does not justify cancelling the Sprint.
C — Incorrect: Temporarily assigning and reallocating individual tasks gives the Product Owner control over work organization, which remains the Developers’ responsibility despite the deadline.
D — Correct: The scope exchange preserves the Sprint Goal, while Developers retain control of their work and stakeholders gain useful daily delivery visibility.
Question 24
Topic: Understanding and Applying the Scrum Framework
Three Scrum Teams are building a new claims service. They share one Product Owner, Product Backlog and Product Goal: reduce claims handling time for small-business customers.
Sprint Review evidence:
- All teams report their selected Product Backlog items as Done.
- Their shared Definition of Done requires code review, passing component unit tests and successful deployment in isolation. Each component passes these checks.
- A cross-component smoke test fails because the components use incompatible message formats. No claim can complete the service’s essential submission-to-decision flow.
The teams plan two more Sprints of component development before a separate integration period. The sponsor supports this plan, arguing:
Most planned items are Done, so the pilot’s technical risk is now low.
Which interpretation should guide the Product Owner’s assessment of the reported completion?
- A. The work is Done because it meets the shared definition; the integration failure should change the pilot forecast rather than the assessment of Increment completion.
- B. The work cannot establish a Done Increment until the pilot demonstrates reduced handling time; successful end-to-end integration would provide necessary but insufficient completion evidence.
- C. The work constitutes three separate Increments; each team’s component can be Done after isolated verification, with cross-component integration assessed before the pilot release.
- D. The work does not yet establish a usable Increment; the shared component checklist is insufficient while the product’s essential flow cannot operate end to end.
Best answer: D
An Increment must be usable and thoroughly verified so that its parts work together. Multiple Scrum Teams working on one product share a Definition of Done that supports this product-level quality. A common checklist is insufficient when it permits incompatible components to be reported as complete.
Here, isolated deployments and unit tests demonstrate local progress, but the failed essential workflow exposes unresolved integration work. The completion counts therefore do not establish a usable Increment or substantiate the sponsor’s low-risk assessment. Deferring integration also delays discovery of further incompatibilities.
The shared Definition of Done and working practices need to make integration and verification part of creating Increments, rather than a later phase. This does not require releasing every Increment to customers. Pilot release and measurement of reduced handling time are separate decisions and observations; neither is a prerequisite for establishing a Done, usable Increment.
Answer choices explained:
A — Incorrect: A shared Definition of Done must support a usable product Increment; agreement on an inadequate checklist does not make integration a release-only concern.
B — Incorrect: Reduced handling time is a customer outcome to inspect; a usable, integrated Increment can be Done before release or fulfillment of the Product Goal.
C — Incorrect: Teams working on one product cannot treat unusable component outputs as separate product Increments merely because each component can be deployed in isolation.
D — Correct: The failed essential workflow demonstrates unresolved product-level integration, so passing the component checklist does not establish the usable Increment Scrum requires.
Question 25
Topic: Understanding and Applying the Scrum Framework
A payments product is midway through a Sprint with this Sprint Goal:
Enable pilot merchants to reconcile daily payments without manual corrections.
Pilot use reveals that duplicate payment events produce incorrect totals. The Developers report that correcting this cannot fit alongside all selected work. A selected export enhancement is not necessary to achieve the Sprint Goal, which remains valuable and achievable.
The Product Owner moves the correction to the top of the Product Backlog and proposes using that ordering decision to replace the export enhancement in the Sprint Backlog.
Which response best respects Scrum accountabilities while addressing the new evidence?
- A. Apply the exchange directly; Product Backlog ordering determines which items remain selected, while Developers determine how to implement them.
- B. Defer the exchange until the next Sprint Planning; Developers’ commitment to the Sprint Goal also commits them to the selected items.
- C. Let Developers settle the exchange independently; their ownership of the Sprint Backlog gives them authority over the business priority of selected work.
- D. Negotiate the exchange with Developers; Product Backlog ordering informs the discussion, while Developers adapt their Sprint Backlog plan to achieve the Sprint Goal.
Best answer: D
The Sprint Backlog is a plan by and for Developers. Product Backlog ordering is the Product Owner’s accountability, but changing that order does not automatically change the current Sprint’s selected scope or delivery plan.
Here, correcting duplicate events is necessary to achieve the Sprint Goal, while the export enhancement could be deferred. The Product Owner and Developers should renegotiate scope using that evidence, with Developers adapting their Sprint Backlog accordingly.
Selected Product Backlog items are a forecast, not an immutable commitment. The Sprint Goal provides the commitment and allows flexibility in the work needed to achieve it. Preserving Developers’ self-management means respecting their control of the plan, not excluding the Product Owner from value-related scope decisions.
Answer choices explained:
A — Incorrect: Product Backlog ordering does not authorize unilateral changes to selected Sprint scope; the Product Owner must collaborate with Developers on the trade-off.
B — Incorrect: The commitment is the Sprint Goal, not a fixed selection of items; deferring the necessary correction would jeopardize that goal.
C — Incorrect: Developers manage their Sprint Backlog, but self-management does not remove the Product Owner from scope negotiations involving product value and priorities.
D — Correct: The emerging work calls for collaborative scope renegotiation, while Developers retain control of their plan for achieving the Sprint Goal.
Questions 26-40
Question 26
Topic: Managing Products with Agility
A company pilots a guided expense-claim capability for employees submitting their first claim. The value hypothesis is that these employees will submit policy-compliant claims without help and spend less total time preparing and correcting them.
Delivery and use:
- All 12 planned improvements meet the Definition of Done and are released. Finance sponsors endorse expansion.
- Of 200 pilot employees, 180 use the capability and 170 reach submission confirmation. Policy validation happens after confirmation.
Results: Each cohort contains 200 first-time claimants with comparable claim complexity.
| Measure | Before pilot | Pilot |
|---|---|---|
| Valid claims submitted without help | 90 | 90 |
| Median effort, independent completers | 20 minutes | 12 minutes |
| Median effort, all claimants | 35 minutes | 35 minutes |
Pilot satisfaction averages 4.7/5 among 60 respondents. Only the 90 employees who independently submitted valid claims were invited to respond.
Finance proposes funding rollout to all business units as a demonstrated customer-value improvement. Which assessment is best supported?
- A. Improved customer experience is demonstrated for the target group; improved independent completion remains unconfirmed.
- B. Delivery and use are demonstrated; improved independent completion and reduced total effort for the target group remain unconfirmed.
- C. Reduced total effort is demonstrated for the target group; improved independent completion remains unconfirmed.
- D. Improved independent completion is demonstrated for the target group; reduced total effort remains unconfirmed.
Best answer: B
Delivered output is not automatically a valuable customer outcome. Meeting the Definition of Done establishes a usable Increment, not that its value hypothesis is true. Here, the intended outcome concerns valid, independent submissions and reduced effort for first-time claimants. Confirmation-screen completion does not establish task success because policy validation follows it.
Independent valid submissions remain at 90 of 200, and median effort across the target group remains 35 minutes. Faster completion among successful claimants is a useful signal, but it does not establish reduced effort across the intended users. Similarly, satisfaction feedback from successful claimants does not represent those who struggled.
The capability may provide benefits worth exploring, but delivery volume, usage, sponsor endorsement, and selected positive feedback do not establish the intended customer outcome.
Answer choices explained:
A — Incorrect: The satisfaction survey excludes unsuccessful claimants and provides no baseline, so it cannot establish improved experience across the target group.
B — Correct: The capability is released and used, but independent valid completion and median effort across all first-time claimants remain unchanged.
C — Incorrect: Effort decreased among independent completers, but the median across all first-time claimants remains 35 minutes, leaving the intended group-wide benefit unconfirmed.
D — Incorrect: Submission confirmation precedes policy validation; valid claims submitted without help remain at 90 of 200, so improved independent completion is not demonstrated.
Question 27
Topic: Managing Products with Agility
A distributor has piloted a Done Increment that lets customers request a different delivery date. The intended outcome is fewer missed deliveries. Achieving this requires warehouse dispatch to update picking plans and an external carrier to revise routes.
Pilot evidence:
- Customers usually complete date-change requests successfully, but the missed-delivery rate has not improved.
- Dispatch staff use the new handoff inconsistently. Carrier route planners report that requests often reach them after routes are fixed.
- The operations director and the carrier’s account manager support expansion. Dispatch staff and route planners have only seen demonstrations of the feature.
The Product Owner can support one further two-week trial before deciding on a wider rollout. The trial will track missed deliveries and additional handling effort.
Which approach would provide the strongest evidence for that rollout decision?
- A. Run a trial across more depots using the existing handoff, with operations and carrier sponsors recruiting participants and reviewing the results.
- B. Run a trial at the pilot depot using a customer-tested request interface, with operations and carrier representatives reviewing the design before it is used.
- C. Run a trial at the pilot depot using a handoff co-designed with dispatch staff and carrier route planners, who inspect and adapt it together.
- D. Run a trial at the pilot depot under service targets agreed by operations and carrier sponsors, using the existing handoff to assess target achievement.
Best answer: C
Stakeholder support must include the operational cooperation on which customer outcomes depend. Successful request submission demonstrates functioning software, not fewer missed deliveries. The evidence points to handoff and adoption uncertainties, so dispatch staff and carrier route planners should help shape and run an end-to-end trial rather than only review a design.
Testing a revised handoff allows these stakeholders to inspect missed deliveries and added handling effort while adapting their working arrangements. This provides evidence about whether customer benefit can be achieved at a workable operational cost. Sponsor endorsement can help secure support, but does not establish that daily coordination will work. Meeting the Definition of Done establishes a usable Increment; realizing value also depends on adoption and outcomes.
Answer choices explained:
A — Incorrect: Broader participation could reveal how widespread the difficulties are, but repeating the existing handoff does not test how to resolve the observed coordination problems.
B — Incorrect: Request completion is already successful; further interface validation addresses a less-supported uncertainty while stakeholder involvement remains limited to reviewing the design.
C — Correct: Involving the people executing both handoffs tests the operational adoption and partner cooperation needed to turn successful requests into fewer missed deliveries.
D — Incorrect: Agreed targets clarify expectations, but retaining the handoff leaves the observed coordination difficulties unaddressed and does not establish practical operational support.
Question 28
Topic: Evolving the Agile Organization
Three products provide travel booking, purchasing, and expense reimbursement. Each has independently developed approval capabilities. Finance proposes consolidating them to reduce duplicated investment.
Evidence:
- Sixty percent of customer organizations use at least two products. Observed administrators repeatedly enter the same approvers and department spending limits.
- Product-specific experiments have demonstrated benefits from different approval journeys: rapid booking decisions, staged purchasing approvals, and efficient reimbursement of completed spending.
- A small shared-workflow pilot reduced duplicated coding, but coordination and cross-product regression-testing effort exceeded those savings. Product-specific changes also took longer.
- The pilot retained separate policy entries, so administrators still repeated their setup work.
The portfolio can fund one further bounded pilot. The priority is customer benefit across the portfolio, taking total engineering effort and responsiveness to customer needs into account.
Which investment direction is best supported?
- A. Pilot separate policy-setup improvements in each product, coordinating priorities through a common roadmap.
- B. Pilot a reusable policy-editor component, keeping policy data and approval workflows within each product.
- C. Pilot shared administrator policy setup, keeping approval workflows specific to each product.
- D. Pilot a common configurable approval workflow, including shared administrator policy setup for all three products.
Best answer: C
Similar capabilities do not necessarily represent duplicated customer value. Investment should distinguish useful commonality from differences that support distinct customer outcomes, then account for the costs of coordination.
Here, repeated entry of common policy information is an observed customer problem. The different approval journeys also have demonstrated benefits. The shared-workflow pilot suggests that consolidating processing can introduce dependencies whose costs outweigh reduced coding effort.
A bounded pilot of shared administrator setup therefore has the strongest evidential basis. It tests the common customer need without requiring consolidation of the differentiated workflows. Measure administrator effort, total engineering and coordination effort, and effects on product-specific outcomes and delivery responsiveness. The evidence supports testing selective sharing, not assuming that either complete centralization or complete independence maximizes portfolio value.
Answer choices explained:
A — Incorrect: Separate improvements preserve responsiveness, but aligning priorities does not address administrators entering the same information across products.
B — Incorrect: Reusing the editor may reduce implementation effort, but separate policy data leaves the observed repeated customer setup unresolved.
C — Correct: This targets the demonstrated cross-product friction while preserving beneficial workflow differences and avoiding expansion of the costly shared-workflow dependency.
D — Incorrect: Adding shared setup addresses customer friction, but extending workflow consolidation retains the coupling whose observed costs exceeded its engineering savings.
Question 29
Topic: Managing Products with Agility
A Scrum Team has a Done Increment that validates supplier-payment data and produces a submission file. The planned release was intended to reduce late payments through a bank partner’s automated-submission service. That service is delayed for at least six weeks, with no reliable launch date.
A partial rollout would replace selected customers’ current preparation workflow while retaining their existing bank-submission route. Rollout is reversible, support costs are negligible, and rollout would not delay the partner integration.
Pilot evidence: A four-week randomized pilot compared the current and partial workflows in representative samples of two customer groups. Average staff time per weekly payment run includes preparation, bank submission, and corrections.
| Customer group | Current workflow | Partial workflow |
|---|---|---|
| Banks accept the downloaded file | 40 minutes | 25 minutes |
| Banks require manual rekeying | 40 minutes | 45 minutes |
Both groups completed validation faster. Customers requiring rekeying expressed stronger demand for release. Neither group showed a detectable change in late-payment rates.
To maximize demonstrated customer benefit over the next four weeks, which release decision should the Product Owner make?
- A. Keep the current workflow for both customer groups until the partner service is available.
- B. Roll out the partial workflow to customers whose banks require manual rekeying.
- C. Roll out the partial workflow to customers whose banks accept the downloaded file.
- D. Roll out the partial workflow to both customer groups during the partner delay.
Best answer: C
A dependency can block an intended benefit without blocking every valuable release. Meeting the Definition of Done establishes that an Increment is usable, not that releasing it benefits every customer segment.
Here, customers whose banks accept the downloaded file can realize a separate benefit before automated submission becomes available. Their total handling time falls from 40 to 25 minutes per run. Waiting four weeks would forgo an hour of savings per customer across four weekly runs.
Customers requiring rekeying experience the opposite result: faster validation is outweighed by effort elsewhere in the workflow. Their stronger expressed demand may indicate an opportunity for the future integrated service, but it does not demonstrate value from the partial workflow now.
The supported decision is therefore a targeted release based on end-to-end customer outcomes, followed by continued inspection as usage and partner availability change.
Answer choices explained:
A — Incorrect: Waiting would forgo a demonstrated 15-minute saving per run for file-upload customers, even though the originally intended late-payment benefit remains unproven.
B — Incorrect: Stronger expressed demand does not offset the observed increase from 40 to 45 minutes per complete payment run for customers requiring rekeying.
C — Correct: File-upload customers save 15 minutes per complete payment run using their existing submission route, creating value independently of the unavailable partner service.
D — Incorrect: Faster validation does not establish an overall benefit for both groups: customers requiring rekeying spend five additional minutes per complete payment run.
Question 30
Topic: Evolving the Agile Organization
A Product Owner and finance lead can fund either build automation or approval delegation as an organizational pilot, but not both. Each pilot covers one comparable product change. Their criterion is the lowest estimated pilot cost per calendar week removed from the cycle between selecting a product hypothesis and obtaining usable customer evidence.
Current cycle: Development takes 6 weeks, waiting for release approval takes 4 weeks, and customer use and evidence collection take 2 weeks.
Pilot forecasts:
| Measure | Build automation | Approval delegation |
|---|---|---|
| Total pilot cost | $15,000 | $24,000 |
| Development | 3 weeks | 6 weeks |
| Release-approval wait | 6 weeks | 2 weeks |
All stages are sequential, and all durations are calendar weeks. Customer use and evidence collection remain 2 weeks under either pilot. Assume no other cost or evidence-quality differences. The forecasts are assumptions to test, not demonstrated effects.
Which funding recommendation follows from their agreed criterion?
- A. Fund approval delegation at an estimated $6,000 per calendar week removed from the end-to-end cycle.
- B. Fund build automation at an estimated $15,000 per calendar week removed from the end-to-end cycle.
- C. Fund build automation at an estimated $5,000 per calendar week removed from the end-to-end cycle.
- D. Fund approval delegation at an estimated $12,000 per calendar week removed from the end-to-end cycle.
Best answer: D
Time-to-Market should be inspected across the chosen product-system boundary. Reducing development time does not necessarily shorten the full learning cycle by the same amount.
The current cycle takes \(6+4+2=12\) weeks. Build automation produces a cycle of \(3+6+2=11\) weeks, saving one week at $15,000 per week saved. Approval delegation produces a cycle of \(6+2+2=10\) weeks, saving two weeks at $12,000 per week saved. Approval delegation therefore meets the stated cost-efficiency criterion despite its higher total pilot cost.
These estimates support selecting an experiment, not claiming realized customer value. Inspect actual elapsed times and customer outcomes to test the assumptions. A shorter learning cycle can improve opportunities to adapt, but it does not establish that the resulting product changes benefit customers.
Answer choices explained:
A — Incorrect: The $6,000 figure divides cost by the original four-week approval wait; the pilot removes only two weeks from the end-to-end cycle.
B — Incorrect: Automation does cost $15,000 per end-to-end week saved, but approval delegation costs $12,000, so automation does not meet the lowest-cost criterion.
C — Incorrect: Dividing $15,000 by the three development weeks saved ignores the two added approval weeks; the full cycle shortens by only one week.
D — Correct: Approval delegation reduces the cycle from 12 to 10 weeks, giving $24,000 divided by two weeks, the lower estimated cost per week saved.
Question 31
Topic: Understanding and Applying the Scrum Framework
A Product Owner for a business-payments product meets with the chief revenue officer, the product’s executive sponsor, who is negotiating two large contracts.
- Current Product Goal: Reduce misdirected first payments by new customers.
- Customer evidence: In sandbox trials with customers’ finance staff, payee confirmation caught incorrect bank details in 8 of 80 first-payment attempts. Misdirected live payments cannot reliably be recovered.
- Commercial evidence: Both prospects report that first-payment setup takes too long. The executive believes their experienced staff could safely skip confirmation, but this has not been tested.
- Experiment capability: Alternative payment flows can be tested in the sandbox without transferring money.
The executive says:
“Make skipping confirmation the default for these customers and put it first. I know what will close these deals.”
Which response in this discussion is best supported by the available evidence?
- A. Review the sales evidence with the executive, retain the current ordering, and explain that Scrum requires the existing Product Goal to be achieved before a different direction can be considered.
- B. Discuss the risk with the executive, prioritize an opt-in live pilot for the two prospects, and use their payment-error rates to decide whether bypassing confirmation should be extended.
- C. Review the commercial opportunity with the executive, abandon the current Product Goal to focus on faster first payments, and prioritize the bypass while tracking contract value and payment accuracy.
- D. Examine the executive’s commercial assumptions alongside the risk evidence, then use a sandbox experiment to test safer alternatives before deciding whether to change direction or reorder the Product Backlog.
Best answer: D
Courage means making the conflict between the requested bypass and the customer outcome explicit, even under executive pressure. Respect means taking the executive’s knowledge of buyers seriously without treating it as conclusive.
The evidence supports a need for faster setup, not the claim that experienced staff can safely skip confirmation. The observed errors and poor recoverability make a live bypass a consequential experiment. Sandbox testing with the prospects can explore whether faster flows can meet their needs while retaining effective protection.
The Product Owner remains accountable for maximizing value and ordering the Product Backlog. Evidence may justify changing direction, including explicitly abandoning the current Product Goal before adopting another. Neither executive authority nor rigid adherence to the existing direction substitutes for inspecting the opportunity and risk.
Answer choices explained:
A — Incorrect: A Product Goal may be abandoned before another is adopted; commitment does not require dismissing evidence that could support a better direction.
B — Incorrect: Opt-in participation does not validate the safety assumption, and a live pilot exposes customers to potentially unrecoverable losses before safer testing.
C — Incorrect: The prospects’ desire for speed does not establish that bypassing confirmation is necessary or sufficiently safe to justify this change in direction.
D — Correct: Examining commercial knowledge and demonstrated payment risk together challenges the proposed solution respectfully while keeping value and ordering decisions with the Product Owner.
Question 32
Topic: Understanding and Applying the Scrum Framework
A Product Owner is ordering the Product Backlog for a self-service onboarding feature. The Product Goal is to reduce staff effort while maintaining customer setup completion rates.
A pilot involved six new customer organizations. All completed setup, and buyers from five said they would pay for the feature. A support specialist attended every session and manually corrected import data for four organizations.
- The sales leader recommends a paid expansion, citing buyer interest.
- The support specialist recommends redesigning onboarding, citing the manual work hidden by the completion results.
- A Developer recommends an import check followed by wider release. The Developer traced the corrections to one import-format problem and believes a small check is feasible, but customers have not used it.
They still disagree after discussing the evidence. The next investment should establish whether customers can complete setup with less staff help.
Which response best applies respect while addressing the Product Goal?
- A. Prioritize the import check for wider release, treating the Developer’s identification of the technical cause as sufficient evidence that customers will need less staff help.
- B. Prioritize a self-service trial of the import check with new customers, measuring completion and staff effort to evaluate whether the proposed remedy works.
- C. Prioritize a paid expansion of the assisted pilot, using purchase commitments to decide whether commercial demand justifies retaining the current level of support.
- D. Prioritize another assisted pilot to develop a common interpretation, postponing a product change until the sales leader, support specialist, and Developer agree.
Best answer: B
Respect means taking each contributor’s knowledge seriously, not treating every conclusion as equally supported or ranking interpretations by seniority. Buyer interest suggests an opportunity. The support specialist exposes effort hidden by the successful completion results. The Developer identifies a plausible remedy, not a demonstrated outcome.
Together, these observations support a focused self-service trial. Measuring completion and staff effort would test whether the proposed import check advances the Product Goal. The small assisted pilot cannot establish that customers will succeed with less help.
The Product Owner remains accountable for Product Backlog ordering. They can explain how each person’s evidence informed the decision and proceed even when recommendations still differ. Shared understanding is useful; unanimous agreement is not a prerequisite.
Answer choices explained:
A — Incorrect: Identifying a technical cause does not demonstrate that the proposed check will reduce staff effort while preserving customers’ ability to complete setup.
B — Correct: The trial combines the commercial opportunity, observed support burden, and technical hypothesis while testing the Product Goal without requiring agreement.
C — Incorrect: A paid assisted pilot would test commercial viability rather than whether customers can complete setup with less staff help.
D — Incorrect: Respect does not require unanimity; repeating assisted setup until everyone agrees postpones testing whether customers can succeed with less help.
Question 33
Topic: Managing Products with Agility
A product helps small service businesses collect invoice payments on time. Its Product Owner must decide whether to fund new customer acquisition with a flat monthly subscription or per-reminder pricing. The strategy is to broaden customer access while sustaining contribution after messaging and support costs.
Early evidence: In an eight-week trial, businesses chose their own offer. Per-reminder pricing attracted more registrations and higher total revenue, but had fewer reminders per paying business and higher total support costs.
The Product Owner proposes this hypothesis:
Per-reminder pricing helps more eligible businesses improve payment timeliness without reducing contribution per eligible business.
Both offers can now be tested concurrently with equivalent functionality and onboarding. The team can obtain invoice records from all recruited businesses, including nonbuyers, and measure usage, payment timeliness, revenue and serving costs over twelve weeks.
Which comparison would best test this hypothesis for new customer acquisition?
- A. Randomly assign eligible prospective businesses to an offer and compare results only among businesses that become paying customers.
- B. Randomly assign current paying businesses to an offer at renewal and compare results across all businesses assigned to each offer.
- C. Randomly assign eligible prospective businesses to an offer and compare results across all businesses assigned to each offer.
- D. Let eligible prospective businesses select an offer and compare results between pricing groups matched on their previous invoice volume.
Best answer: C
A pricing hypothesis should connect customer outcomes with business economics. More registrations suggest broader access, but do not establish improved payment timeliness. Higher revenue may be offset by support and messaging costs. Fewer reminders could indicate either reduced useful activity or more efficient collection; the customer outcome distinguishes these interpretations.
Randomly assigning eligible prospects to concurrent offers reduces differences in customer mix. Keeping every assigned business in the comparison preserves the effects of pricing on whether businesses buy at all. Comparing only purchasers can make an offer appear successful by excluding the businesses it discourages.
The relevant evidence is improvement in payment timeliness across the eligible population together with contribution after serving costs per eligible business. This supports a context-specific pricing decision, not a universal preference for subscriptions or usage-based pricing. A twelve-week result would still leave longer-term retention and economics open to further inspection.
Answer choices explained:
A — Incorrect: Restricting analysis to purchasers excludes businesses that pricing discourages from buying, potentially masking reduced access and distorting comparisons of outcomes and contribution.
B — Incorrect: Existing customers have already crossed the initial purchasing barrier, so their renewal behavior does not directly test expanded access for prospective businesses.
C — Correct: Random assignment and analysis of all assigned prospects capture pricing effects on access, customer outcomes and contribution across the intended acquisition population.
D — Incorrect: Matching invoice volume reduces one difference, but willingness to pay and expected usage can still influence selection and confound the pricing comparison.
Question 34
Topic: Managing Products with Agility
An organization must allocate next year’s discretionary funding for a scheduling product. The Product Owner finds that executives, sales and Developers all use the same vision slide:
Remove the friction from arranging services.
Asked separately what the product should primarily become over the next two years, they describe:
- Executives: An operations suite for large service chains, improving utilization across locations.
- Sales: A tailored booking service for independent specialists, strengthening premium relationships with their clients.
- Developers: A self-service platform for software providers, enabling scheduling to be embedded in their products.
All three groups endorse the next release, whose content is largely determined by existing contractual commitments.
Which judgment is best supported about their shared understanding of the product’s purpose?
- A. Shared purpose is demonstrated by the scheduling-friction theme; the different futures represent market opportunities that can be sequenced within one product.
- B. Shared purpose cannot yet be assessed; the different futures require customer validation before the groups’ understanding of the vision can be judged.
- C. Shared purpose is not yet demonstrated; the common release commitment leaves different intended beneficiaries and outcomes unresolved for discretionary investment.
- D. Shared purpose is demonstrated by the next-release agreement; the different futures represent implementation approaches within an already understood product direction.
Best answer: C
A shared product vision gives people a common understanding of the future the product is intended to create. It does not require identical feature preferences, but it should help people reason about customers, outcomes and consequential trade-offs.
Here, executives emphasize service-chain utilization, sales emphasizes premium relationships for independent specialists, and Developers emphasize an embedded platform for software providers. Agreement on the next release provides limited evidence of common purpose because contracts largely determine that work.
Stronger evidence would come from how the groups assess unfamiliar investment trade-offs and connect their reasoning to the intended future. They may propose different solutions while demonstrating a common purpose. Whether that shared direction actually creates customer and business value remains a separate matter for empirical validation.
Answer choices explained:
A — Incorrect: A broad theme can accommodate several directions without establishing agreement about which customers and outcomes should guide investment trade-offs.
B — Incorrect: Customer experiments test whether a direction creates value; they are not a prerequisite for comparing what stakeholders understand that direction to mean.
C — Correct: The groups describe different primary beneficiaries and benefits, while contractual commitments explain their agreement on near-term work.
D — Incorrect: Agreement on contract-driven delivery does not establish common direction, and differing primary customers and benefits go beyond implementation approaches.
Question 35
Topic: Managing Products with Agility
A Product Owner is advising a partner considering a nonrefundable launch event at the end of week seven. Launch requires completing all 33 remaining Product Backlog items.
Delivery evidence:
- The remaining items are comparable in size and work type to the historical items. Team capacity is expected to remain unchanged.
- Items meeting the Definition of Done over eight consecutive weeks were: 3, 11, 2, 9, 4, 12, 1, and 10.
- A history-based forecast presents a five-to-seven-week delivery range. It estimates a 50% chance of completion by the end of week five and an 85% chance by the end of week seven, assuming comparable scope and workflow.
Planned change: Starting next week, the team will reduce its work in progress limit from 10 items to eight. There are no observations yet of this change’s effect on throughput.
Which interpretation should the Product Owner communicate to represent the launch risk most accurately?
- A. Seven weeks is an 85% completion date under the historical conditions; the planned work in progress limit change does not yet support a quantified improvement.
- B. Seven weeks is a 92.5% completion date under the historical conditions; the 85% range leaves 7.5% of completions beyond its upper endpoint.
- C. Seven weeks is a 35% completion date under the historical conditions; the difference between the endpoint probabilities measures the chance of meeting that date.
- D. About six weeks is an 85% completion date under the new conditions; the 20% lower work in progress limit justifies a proportionally shorter forecast.
Best answer: A
A throughput-based delivery forecast describes uncertainty under assumptions about comparable future work and delivery conditions. Here, the historical model estimates 85% completion by week seven, leaving an estimated 15% chance of finishing later under those assumptions. It does not establish a guaranteed launch date.
The endpoints are cumulative estimates: 50% completion by week five and 85% by week seven. Their difference represents completion after week five and by week seven, rather than confidence in the upper date.
Lowering the work in progress limit changes an operating policy. It may improve flow, but it does not automatically shorten delivery time by 20%. The historical result remains a conditional baseline; observations under the changed workflow should inform an updated forecast.
Answer choices explained:
A — Correct: The seven-week estimate is conditional on comparable delivery conditions; no observed results yet justify assigning an earlier date the same completion probability.
B — Incorrect: The reported probabilities are cumulative completion estimates, not the boundaries of a central 85% interval with equal probability in each tail.
C — Incorrect: The 35-percentage-point difference concerns completion after week five and by week seven, not all completion by week seven.
D — Incorrect: Reducing a work in progress limit is not an observed throughput improvement and does not establish a proportional reduction in completion time.
Question 36
Topic: Managing Products with Agility
A Scrum Team develops a billing platform. Four working days remain in its Sprint. The Sprint Goal is to let invited finance users activate their accounts without support. Selected work includes activation-flow changes and an administrator invitation dashboard.
New evidence:
- An existing customer’s first high-volume billing run reveals a defect blocking invoice submission. Its contractual submission cutoff is two working days away. Late invoices will delay payment by a month, and support’s manual workaround can handle only 10% of affected invoices.
- Developers forecast that deferring the dashboard would allow them to deliver a repair meeting the Definition of Done before the cutoff and complete the activation changes within the Sprint. Completing all three is unlikely.
- The activation outcome remains important for a customer rollout next week.
Which response should the Product Owner take?
- A. Retain the Sprint Goal and selected work, use the manual workaround, and order the repair first for consideration at the next Sprint Planning.
- B. Agree with the Developers to defer the dashboard for the repair; they adapt the Sprint Backlog while retaining the Sprint Goal.
- C. Cancel the Sprint and propose restoring invoice submission as the next Sprint Goal, allowing the Scrum Team to replan the remaining activation work.
- D. Decide the scope exchange as Product Owner, replace the dashboard with the repair in the Sprint Backlog, and have Developers revise their implementation plan.
Best answer: B
The Sprint Goal is a commitment; the selected Product Backlog items are a forecast. Urgent work need not automatically wait until the next Sprint. As more is learned, Developers and the Product Owner can clarify and renegotiate scope without endangering the Sprint Goal or reducing quality.
Here, deferring the dashboard provides a credible way to address the customer’s deadline while still achieving the activation outcome. The Product Owner contributes the customer impact and product-value trade-offs, while Developers adapt their Sprint Backlog and determine how to deliver the work. Ordering the repair highly in the Product Backlog would not itself change their Sprint plan.
Only the Product Owner can cancel a Sprint when its goal becomes obsolete. A valuable, achievable goal does not become obsolete merely because urgent work arrives.
Answer choices explained:
A — Incorrect: The next Sprint begins after the customer’s cutoff, and the workaround leaves most invoices blocked despite a feasible scope trade.
B — Correct: The scope exchange addresses the imminent customer loss while preserving an achievable Sprint Goal and the Developers’ ownership of their plan.
C — Incorrect: Urgent work does not itself make a Sprint Goal obsolete; the activation outcome remains valuable and achievable alongside the repair.
D — Incorrect: Accountability for product value and Product Backlog ordering does not authorize the Product Owner to unilaterally change the Developers’ Sprint Backlog.
Question 37
Topic: Managing Products with Agility
A software company authorizes up to $360,000 over six months to increase 30-day activation of new small-business accounts from 45% to 60%. The activation outcome is the Scrum Team’s Product Goal. The sponsor delegates product investment choices within these boundaries to the Product Owner. The supporting business case forecasts a setup wizard, tutorial videos, and a progress dashboard.
Evidence after two months:
- Activation remains near 45%.
- Customer interviews point to data-import problems. A 12-account prototype trial suggests validation checks could help, but their effect on activation is untested.
- A wider trial fits within the spending cap. Substantial investment in validation would require dropping at least one planned feature.
- No contractual or regulatory requirement mandates the listed features.
Department managers object:
The feature list was the basis for funding, so it must be delivered before we fund a different solution.
Which response is best supported by the authorization and available evidence?
- A. Commit the remaining investment to import validation instead of the listed features, measuring activation after delivery to assess whether the replacement succeeds.
- B. Run the wider trial under the current authorization, allowing its results to change which features receive the remaining investment.
- C. Request renewed authorization before the wider trial, treating a potential replacement of a listed feature as a change to the sponsors’ approved scope.
- D. Run the wider trial under the current authorization, retaining all originally listed capabilities as required scope when applying its results.
Best answer: B
An outcome target and a spending ceiling constrain an investment; they do not automatically make the proposed features mandatory. Here, the sponsor delegates solution choices to the Product Owner, and the listed features have no independent contractual or regulatory status. Replacing a feature does not change the activation Product Goal.
Import validation remains a value hypothesis. A promising prototype trial does not establish improved 30-day activation. A wider, bounded trial can reduce uncertainty before committing the remaining investment. The Product Owner can then adapt Product Backlog ordering and feature selection within the approved boundaries, making evidence, spending, and tradeoffs transparent to stakeholders. Accountability concerns maximizing product value, not protecting an initial feature forecast.
Answer choices explained:
A — Incorrect: The pilot has not demonstrated an activation improvement, so committing the remaining investment would prematurely lock funding into another unproven solution.
B — Correct: Testing the alternative supports an evidence-based investment decision while preserving the activation target, spending cap, and delegated decision authority.
C — Incorrect: The sponsor delegated product choices within the outcome and budget boundaries; replacing a proposed feature does not itself exceed that authority.
D — Incorrect: Retaining every original capability converts a feature forecast into mandatory scope and restricts adaptation even if evidence favors a different solution.
Question 38
Topic: Managing Products with Agility
An accounting product’s Product Goal is to reduce mid-sized customers’ total staff hours spent on monthly reconciliation. Automated matching and in-product sign-off were released two months ago. Further investment depends on evidence of progress toward that goal.
Evidence:
- All 100 eligible firms can access the capability; 72 enabled it, and 18 migrated their account mappings and reconciliation history.
- Most migrated firms complete matching faster but still repeat reconciliation in spreadsheets used for official sign-off. Their total reconciliation hours remain near baseline.
- Four migrated firms moved sign-off into the product and report 25% fewer total reconciliation hours. They volunteered and have simpler approval processes than typical customers.
The Product Owner can fund one bounded experiment across two monthly closes. It will use representative firms, a comparison group, and total reconciliation hours as the primary outcome.
Which experiment should the Product Owner prioritize to test whether the released capability can deliver the intended value?
- A. Test additional matching rules that automate more transaction categories within the firms’ existing monthly reconciliation process.
- B. Test a reconciliation dashboard that helps finance managers coordinate approvals and monitor progress through their existing sign-off process.
- C. Test an assisted migration program that helps finance managers move reconciliation and sign-off from parallel spreadsheets into the product.
- D. Test a guided onboarding flow that helps more firms activate and navigate the existing matching and sign-off capability.
Best answer: C
Feature availability is an output; value realization requires a beneficial customer outcome. Here, faster automated matching has not reduced total reconciliation effort for customers who continue the parallel spreadsheet workflow.
Assisted migration combined with changing sign-off practices directly tests the strongest hypothesis supported by the evidence: customers may need to change how they work before the released capability produces its intended benefit.
The four successful firms provide encouraging evidence, not proof that the benefit generalizes. They self-selected and have simpler approval processes. Testing with representative firms and a comparison group helps assess whether broader customers can achieve similar reductions. The Product Owner can then use the outcome evidence to decide whether to expand adoption support, adapt the capability, or reconsider further investment.
Answer choices explained:
A — Incorrect: Expanded coverage could improve matching efficiency, but existing matching improvements have not reduced total hours where customers retain parallel reconciliation.
B — Incorrect: A dashboard could improve coordination, but preserving the existing sign-off process does not directly test the observed obstacle of duplicated reconciliation work.
C — Correct: This tests whether overcoming migration barriers and replacing duplicate work enables representative customers to achieve the intended reduction in total reconciliation effort.
D — Incorrect: Improved onboarding could increase uptake, but even migrated firms duplicate reconciliation for sign-off; activation and navigation do not directly address that observed barrier.
Question 39
Topic: Managing Products with Agility
A Product Owner for an invoice-management product is investigating a customer’s workflow. The agreed outcome for the next investment is fewer avoidable late-payment fees.
Interviews: Five accounts-payable clerks request the scheduled Excel export they used in their previous system.
“Our old system emailed the file every morning. Here I spend an hour rebuilding it. We need that export.”
Observed workflow:
- Clerks combine invoice due dates from the product with payment-approval statuses from their bank portal, then contact approvers for payments due that day.
- The finance director uses the completed spreadsheet for a weekly cash review.
- Reviewed invoice amounts matched across systems, and approved payments were submitted promptly.
- Payments that incurred late fees still lacked approval at the bank’s 15:00 same-day cutoff.
Which working problem statement is best supported for further discovery?
- A. Clerks need to prepare consolidated payment information faster so the finance director can complete the weekly cash review with current data.
- B. Clerks need to reconcile invoice amounts across systems so payment batches contain consistent values before they are submitted to the bank.
- C. Clerks need to identify payments awaiting approval early enough to obtain approval before the bank’s same-day payment cutoff.
- D. Clerks need to shorten the submission process for approved payments so completed batches reach the bank before its same-day payment cutoff.
Best answer: C
A feature request proposes a solution; a useful problem statement captures the job, context and desired outcome. Here, clerks assemble due dates and approval statuses to identify payments requiring intervention before a deadline. The reviewed late fees concern missing approvals, making timely identification and follow-up the strongest working focus for discovery.
The scheduled export remains a credible solution hypothesis. Familiarity and manual copying costs make it worth considering, not automatically worth building or rejecting. Further discovery should examine when clerks notice missing approvals, what prevents timely intervention and whether an export would address those difficulties. Candidate solutions should be evaluated by their contribution to timely payments and fewer avoidable fees, rather than by whether they reproduce the old spreadsheet.
Answer choices explained:
A — Incorrect: The weekly report is a real use of the spreadsheet, but the reviewed fees relate to missing approvals, not reporting timeliness.
B — Incorrect: The reviewed invoice amounts matched, so the evidence does not support amount reconciliation as the unmet need behind these late fees.
C — Correct: Identifying and obtaining missing approvals before the cutoff addresses the observed workflow and the failure associated with the reviewed late fees.
D — Incorrect: Approved payments were submitted promptly; the observed gap concerned obtaining approval, not submitting payments that were ready.
Question 40
Topic: Evolving the Agile Organization
A Scrum Team develops merchant-onboarding software. A review finds:
- Done Increments are delivered regularly, but the proportion of merchants requiring setup assistance has not fallen.
- Recent rework resulted from conflicting Sales and Operations requests.
- The Product Owner orders individual requests, but no target customer outcome has been agreed.
An engineering director outside the Scrum Team has relevant technical expertise and proposes:
Make the Product Owner specify how each Product Backlog item will be implemented and assign it to a named Developer.
The Product Owner will work with stakeholders and the Scrum Team to agree on a measurable onboarding outcome and clarify existing organizational constraints. Management also wants to use the director’s expertise to strengthen accountability for results.
Which arrangement for implementation decisions best supports that aim?
- A. The director contributes design advice, the Product Owner approves implementation plans, and Developers decide work allocation and task sequencing.
- B. The director contributes design advice, the Product Owner orders the Product Backlog, and Developers decide implementation and work allocation.
- C. The director approves implementation plans, the Product Owner orders the Product Backlog, and Developers decide work allocation and task sequencing.
- D. The director contributes design advice, the Product Owner assigns work to individuals, and Developers decide implementation and task sequencing.
Best answer: B
Product leadership establishes purpose, desired outcomes, product priorities, and clear constraints. It does not require the Product Owner to prescribe implementation or assign work to individuals.
Here, conflicting requests and the absence of an agreed customer outcome reveal a product-direction gap. Delivering Done Increments demonstrates usable work, not necessarily improved customer results. The Product Owner should use the onboarding outcome to guide Product Backlog ordering and communicate trade-offs.
The director’s expertise remains valuable as advice that Developers can evaluate. Within organizational constraints, Developers decide how to implement the work and organize themselves. Inspecting onboarding results together creates accountability through transparency and adaptation rather than through individual task assignments or technical approval gates.
Answer choices explained:
A — Incorrect: Requiring Product Owner approval of implementation plans transfers implementation authority away from Developers, even though they retain control over task allocation.
B — Correct: The director’s expertise informs implementation without controlling it, while the Product Owner directs product priorities and Developers retain responsibility for organizing their work.
C — Incorrect: Technical expertise supports collaboration, but making the director an implementation approval gate removes decision authority from Developers rather than strengthening their self-management.
D — Incorrect: Assigning work to individual Developers replaces their self-management; the Product Owner’s accountability for value does not include allocating their work.
Turn the result into the next task
| What happened | Useful next step |
|---|---|
| The concept was unfamiliar | Read the relevant official source and explain a new example |
| You missed the deciding condition | Compare the supported conclusion with the exact condition you overlooked |
| You guessed correctly | Review it as uncertainty, not established mastery |
| You recognized the answer | Treat that attempt as revision; use different questions for a fresh check |
| One area was weak despite a high overall score | Use targeted app practice, then return to a new mixed set |
The official pass score is 85%, but reaching it on this selected-response set does not validate readiness for the official assessment. Our set does not replicate the undisclosed partial-credit method. Understand what practice scores can and cannot show .
Continue in PM Mastery
Use the app for varied mixed sets, topic practice, explanations and saved progress. A paid PM Mastery pass or subscription includes this bank and the other PM Mastery banks for its access period; the static questions on this page stay free to read.