I85PREP
⌘ K
EXIN Agile Scrum Product Owner Bridge study materials
EXIN Agile Scrum Product Owner Bridge study resources

EXIN Agile Scrum Product Owner Bridge practice questions

One question at a time. Build your EXIN Agile Scrum Product Owner Bridge understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Agile Way of Thinking

A Product Owner is asked to describe the core of the Agile way of thinking to a new stakeholder. Which statement best captures it?

  1. Maximize the number of features delivered per sprint regardless of value to the customer
  2. Deliver working increments early and often, learning from feedback rather than freezing all requirements up front Correct answer.
  3. Follow the original plan precisely and treat any deviation as a failure of the team
  4. Document every requirement in full detail before development starts so that change is eliminated

Explanation

Agile thinking favors iterative delivery of working increments and deliberate use of feedback to steer the product. Change is treated as expected and valuable, not as a defect in planning. Detailed up-front specification and plan conformity belong to predictive approaches.

Question 2Agile Way of Thinking

In Scrum, which artifact is the Product Owner primarily accountable for maximizing the value of?

  1. The Product Backlog Correct answer.
  2. The Sprint Backlog
  3. The Increment burn-down chart
  4. The Definition of Done

Explanation

The Product Backlog is the Product Owner's artifact and the single source of work for the product; ordering it to maximize value is a core accountability. The Sprint Backlog belongs to the Developers, and the Definition of Done is a shared quality commitment.

Question 3Agile Way of Thinking

A stakeholder asks why the Scrum Team should release a usable Increment at least once per Sprint. Which rationale fits Agile thinking best?

  1. It removes the need for a Definition of Done
  2. It guarantees the release will be defect-free
  3. It shortens the Sprint so that fewer items are needed
  4. It enables early feedback and value realization while risk stays small Correct answer.

Explanation

Frequent Increments let real users and stakeholders respond early, so value arrives sooner and the cost of being wrong stays bounded. Feedback gathered this way informs the next Product Backlog ordering decision. It does not guarantee defect-free releases nor replace quality agreements.

Question 4Agile Way of Thinking

Which pair of values from the Agile Manifesto is stated correctly?

  1. Comprehensive documentation over working software
  2. Individuals and interactions over processes and tools Correct answer.
  3. Contract negotiation over customer collaboration
  4. Following a plan over responding to change

Explanation

The Agile Manifesto values individuals and interactions above processes and tools, while still recognizing the value of the latter. The other pairings invert the manifesto's stated preference. Remembering the direction of each pairing is essential for Product Owners justifying Agile choices.

Question 5Agile Way of Thinking

A Product Owner keeps the Product Backlog ordered by business value, risk, and dependencies. Which Agile principle does this behavior most directly express?

  1. Deliver working software frequently, from a couple of weeks to a couple of months
  2. Simplicity: maximizing the amount of work not done is essential Correct answer.
  3. Build projects around motivated individuals and trust them to get the job done
  4. Working software is the primary measure of progress

Explanation

Ordering work so that only the highest-value, most necessary items are pursued reflects the principle of maximizing the work not done. The Product Owner removes low-value items rather than filling capacity. The other principles concern cadence, motivation, and progress measurement.

Question 6Agile Way of Thinking

A Product Owner receives a request for a large, poorly understood feature. What is the most Agile-aligned first step?

  1. Add the request to the bottom of the Product Backlog and wait for capacity
  2. Ask the Developers to produce a complete technical design before any discussion
  3. Slice the request into small, testable items and validate the riskiest assumptions early Correct answer.
  4. Commit the full feature to the next Sprint so the stakeholder sees responsiveness

Explanation

Agile thinking reduces uncertainty through small, validated increments, so slicing the request and testing the riskiest assumptions first limits wasted effort. Committing an unclear large item to a Sprint invites failure. Deferring indefinitely ignores potential value, and a full design up front contradicts emergent design.

Question 7Agile Way of Thinking

During a refinement session, Developers say an item cannot be estimated because acceptance criteria are unclear. What should the Product Owner do?

  1. Escalate to senior management to decide the estimate
  2. Estimate the item on their behalf so the Sprint can proceed
  3. Clarify the intent and acceptance criteria collaboratively with the Developers Correct answer.
  4. Remove the item from the Product Backlog permanently

Explanation

The Product Owner brings product intent and collaborates with Developers to make items transparent enough to order and size. Estimation itself remains the Developers' responsibility, so the Product Owner clarifies rather than estimates. Permanent removal or escalation bypasses the collaboration Scrum prescribes.

Question 8Agile Way of Thinking

How does the Scrum framework treat the traditional role of project manager?

  1. It assigns project management duties to the Scrum Master
  2. It retains a dedicated project manager inside the Scrum Team
  3. It distributes management responsibilities across the three accountabilities Correct answer.
  4. It requires an external PMO to manage each Sprint

Explanation

Scrum has no project manager role; leadership and management work is distributed among the Product Owner, Scrum Master, and Developers. The Scrum Master facilitates and coaches rather than managing the project. External bodies may support the organization but do not manage Sprints on the team's behalf.

Question 9Agile Way of Thinking

A Product Owner wants to apply the principle of self-organizing teams. Which action is consistent with it?

  1. Approve each developer's daily task list before work begins
  2. Instruct the team to follow a fixed task sequence defined by the Product Owner
  3. Let the Developers decide how to turn selected items into an Increment Correct answer.
  4. Assign each Product Backlog item to a specific developer at refinement

Explanation

Self-organization means the people doing the work decide how to do it, including task breakdown and technical approach. The Product Owner sets what and why through ordering and the Sprint Goal. Prescribing tasks or approving daily lists undermines that autonomy.

Question 10Agile Way of Thinking

Which statement about the Product Goal is correct?

  1. It is set by the Scrum Master to protect the team's focus
  2. It is a long-term objective for the Scrum Team that gives the Product Backlog direction Correct answer.
  3. It is a mandatory deliverable that must be completed within one Sprint
  4. It replaces the Sprint Goal once the first Sprint ends

Explanation

The Product Goal describes a future state of the product and provides a target the Product Backlog moves toward. It is longer-lived than a Sprint Goal and does not have to be achieved in one Sprint. The Product Owner is accountable for developing and communicating it.

Question 11Agile Way of Thinking

A team's Definition of Done is far weaker than the organization's quality standards. What is the most appropriate response?

  1. Suspend the Definition of Done until the next release
  2. Allow the weaker definition so velocity appears higher
  3. Require the Developers to strengthen the Definition of Done to meet organizational standards Correct answer.
  4. Replace the Definition of Done with a checklist maintained by the Product Owner alone

Explanation

The Definition of Done is a formal quality commitment, and when organizational standards exist the team's definition must at minimum meet them. Weakening it to inflate throughput produces false transparency. It is owned by the Developers as a shared agreement, not by the Product Owner alone.

Question 12Agile Way of Thinking

Which situation best illustrates empirical process control in Scrum?

  1. Progress is reported from percentage-complete estimates rather than the Increment
  2. Decisions are based on inspected artifacts and observed outcomes, then adjusted Correct answer.
  3. The team follows the initial plan even when Sprint data show it is no longer viable
  4. The Product Owner approves changes only at the annual planning cycle

Explanation

Empiricism rests on transparency, inspection, and adaptation, so decisions follow what is actually observed in artifacts and results. Sticking to a stale plan or waiting for annual cycles ignores new evidence. Percentage-complete reporting is not an empirical substitute for a real Increment.

Question 13Agile Way of Thinking

An organization wants to adopt Agile thinking but keeps rewarding managers for early, detailed commitments. What is the most accurate assessment?

  1. This is fine because Agile also requires fixed commitments
  2. The reward system conflicts with Agile values and will undermine the adoption Correct answer.
  3. Only the Scrum Master needs to change behavior for adoption to succeed
  4. The conflict disappears once the team uses a Scrum board

Explanation

Agile adoption depends on the surrounding system of incentives and measures aligning with iterative, feedback-driven work. Rewarding detailed early commitments pushes teams back toward predictive behavior regardless of ceremonies used. Tools such as boards do not resolve that misalignment.

Question 14Agile Way of Thinking

A Product Owner must choose between two backlog items for the next Sprint. Item A delivers revenue next month; item B removes a risk that could invalidate the whole product direction. Which reasoning is most consistent with Agile thinking?

  1. Choose both and split them across two Sprint Goals
  2. Choose the risk-reduction item when the risk could invalidate future value, then reassess Correct answer.
  3. Choose neither until a full cost-benefit analysis is complete
  4. Always choose revenue first because value is measured only in money

Explanation

Agile ordering weighs value against risk, and an existential risk can outweigh near-term revenue because it threatens all later value. Once that uncertainty is reduced, the ordering is revisited with better information. A Scrum Team pursues one Sprint Goal per Sprint, so splitting is not the answer.

Question 15Agile Way of Thinking

Which statement about the relationship between the Sprint Goal and the Product Goal is accurate?

  1. The Sprint Goal must be identical to the Product Goal in every Sprint
  2. The Sprint Goal is a step toward the Product Goal and may be adjusted as more is learned Correct answer.
  3. The Sprint Goal is owned by the Scrum Master and the Product Goal by the Developers
  4. The Product Goal is redefined at every Sprint Review

Explanation

The Sprint Goal gives the Sprint a coherent purpose that moves the product toward its longer-term Product Goal. Both are revisited as understanding grows, but they are distinct in scope. Ownership sits with the Developers for the Sprint Goal and the Product Owner for the Product Goal.

Question 16Agile Way of Thinking

A stakeholder insists that the Product Owner approve every code change to protect quality. Which response best reflects Agile thinking?

  1. Decline, because quality is only the Scrum Master's concern
  2. Accept, because the Product Owner owns all quality decisions
  3. Decline, because technical quality is the Developers' accountability within the Definition of Done Correct answer.
  4. Accept, because approval gates shorten feedback loops

Explanation

Scrum separates accountabilities: the Developers own technical quality and the Definition of Done, while the Product Owner focuses on value and ordering. Approval gates slow feedback and duplicate responsibility. The Scrum Master coaches on process rather than owning quality.

Question 17Agile Way of Thinking

Which behavior most clearly demonstrates servant leadership by a Scrum Master?

  1. Deciding the order of Product Backlog items
  2. Reporting team velocity to management without the team's involvement
  3. Directing the Developers' daily task assignments
  4. Removing impediments and coaching the team toward self-management Correct answer.

Explanation

Servant leadership means helping others succeed by removing obstacles and building capability rather than commanding. The Scrum Master serves the team and organization in this way. Ordering the backlog is the Product Owner's work, and task assignment belongs to the Developers.

Question 18Agile Way of Thinking

A new Product Owner asks how Scrum handles requirements that will certainly change. What is the most accurate answer?

  1. Requirements are replaced by the Definition of Done
  2. Requirements are frozen at project start to protect the plan
  3. Requirements live in the Product Backlog and are refined and reordered continuously Correct answer.
  4. Requirements are documented once and then removed from the backlog

Explanation

In Scrum the Product Backlog is a living artifact that is refined and reordered as knowledge grows, which is how change is absorbed without derailing delivery. Freezing requirements or documenting once contradicts empiricism. The Definition of Done concerns quality, not requirements.

Question 19Agile Way of Thinking

An Increment meets the Definition of Done but the Product Owner decides not to release it. What does Scrum say about this?

  1. The Increment must be released immediately or it is not done
  2. The decision to release is separate from being done; value realization can be deferred Correct answer.
  3. The Increment must be discarded because it was not released
  4. The Developers must revert the work to the Product Backlog

Explanation

Being done and being released are distinct decisions; a done Increment is usable and may be released when it best serves value. The Product Owner weighs timing against market and stakeholder considerations. Discarding or reverting done work would waste validated effort.

Question 20Agile Way of Thinking

Which practice best reflects the Agile principle of sustainable pace?

  1. Increasing Sprint length each time the team falls behind
  2. Maintaining a consistent workload so the team can sustain delivery indefinitely Correct answer.
  3. Measuring performance by hours worked per week
  4. Adding overtime whenever a Sprint Goal is at risk

Explanation

Sustainable pace means the team works at a level it can maintain over time, protecting quality and predictability. Overtime to rescue a Sprint trades short-term output for long-term burnout. Sprint length is fixed for consistency, and hours worked are not a measure of progress.

Question 21Agile Way of Thinking

A Product Owner is tempted to accept every incoming request into the current Sprint to keep stakeholders happy. Which consequence is most likely and most relevant to Agile thinking?

  1. The Definition of Done becomes unnecessary
  2. Velocity rises because more work is in progress
  3. Focus on the Sprint Goal erodes and predictability falls Correct answer.
  4. The Sprint Review can be skipped

Explanation

Protecting the Sprint Goal is what makes the Sprint a stable period of focus; constant scope injection fragments effort and destroys predictability. More work in progress does not raise throughput. The Definition of Done and Sprint Review remain required regardless of scope pressure.

Question 22Agile Way of Thinking

How does Scrum's view of documentation differ from a documentation-heavy predictive approach?

  1. Scrum forbids written documentation of any kind
  2. Scrum values documentation while preferring working software as the primary measure Correct answer.
  3. Scrum requires a complete specification before the first Sprint
  4. Scrum treats documentation as more valuable than the Increment

Explanation

The Agile Manifesto values working software over comprehensive documentation while still recognizing documentation's worth. Scrum teams produce as much documentation as genuinely adds value. Neither a total ban nor a mandatory full specification reflects that balance.

Question 23Agile Way of Thinking

A Product Owner wants to reduce batch size of delivered work. Which action aligns with Agile thinking?

  1. Increase the Sprint length to fit larger batches
  2. Deliver smaller slices more frequently so feedback arrives sooner Correct answer.
  3. Delay all releases until the full roadmap is complete
  4. Combine several related features into one large release to reduce overhead

Explanation

Smaller batches shorten the feedback loop, lower risk per release, and make value visible earlier. Large combined releases delay learning and increase the cost of being wrong. Longer Sprints or waiting for the full roadmap both enlarge batches rather than reduce them.

Question 24Agile Way of Thinking

Which statement about the Scrum values is most accurate in the context of Product Backlog decisions?

  1. Openness requires publishing every private stakeholder conversation verbatim
  2. Focus means the Product Owner should avoid speaking with stakeholders
  3. Commitment means the scope selected for a Sprint can never change
  4. Courage allows the Product Owner to say no to low-value requests and keep ordering honest Correct answer.

Explanation

Courage supports the Product Owner in declining low-value work and defending a transparent ordering even under pressure. Focus concerns concentrating on the Sprint Goal, not avoiding stakeholders. Openness and commitment do not mean verbatim disclosure or frozen scope.

Question 25Agile Way of Thinking

A team claims to be Agile but delivers one large release per year with no intermediate feedback. Which diagnosis is most defensible?

  1. The team is Agile because it uses Sprints internally
  2. The cadence is irrelevant as long as the Definition of Done is met
  3. The delivery cadence contradicts Agile's emphasis on frequent value and feedback Correct answer.
  4. The team is Agile because it has a Product Owner

Explanation

Agile thinking requires frequent delivery of valuable increments so that feedback can shape the product; an annual release removes that mechanism. Internal ceremonies alone do not make an organization Agile. Meeting the Definition of Done is necessary but does not substitute for timely value delivery.

Question 26Agile Way of Thinking

A Product Owner is asked to describe the core idea of Agile thinking to new stakeholders. Which statement best captures that core idea?

  1. Deliver working product increments frequently and use the resulting feedback to steer the product. Correct answer.
  2. Maximize the number of features delivered per Sprint regardless of their value.
  3. Produce a complete requirements specification before any development work begins.
  4. Assign each team member a fixed set of tasks defined at the start of the project.

Explanation

Agile thinking favors frequent delivery of working product and short feedback loops so that decisions are based on real evidence rather than on assumptions captured in documents. Detailed up-front specifications, output-focused feature counts, and fixed task assignments all reflect predictive control rather than empirical, value-driven steering.

Question 27Agile Way of Thinking

A Product Owner is prioritizing the Product Backlog. Which ordering best reflects Agile thinking about value?

  1. Items requested by the most senior stakeholder are placed first.
  2. Items that deliver the greatest value and learning soonest are placed first. Correct answer.
  3. Items that are easiest for the Developers to build are placed first.
  4. Items that have been in the backlog longest are placed first.

Explanation

Agile thinking directs the Product Owner to order the backlog to maximize value and early learning, so that the most valuable and informative work is delivered soonest. Ordering by ease, age, or stakeholder seniority substitutes convenience or politics for value.

Question 28Agile Way of Thinking

A Product Owner is explaining why Scrum favors empirical process control. Which situation best demonstrates that control?

  1. The team follows a detailed plan created at project start and reports percentage complete against it.
  2. The Product Owner approves each Developer's daily task list before work may proceed.
  3. The team inspects a working Increment at the Sprint Review and adapts the Product Backlog based on what it learns. Correct answer.
  4. The organization freezes the Product Backlog for the duration of the release to avoid scope changes.

Explanation

Empirical process control rests on transparency, inspection, and adaptation; inspecting a real Increment and adapting the backlog is exactly that cycle. Following a fixed plan, approving daily task lists, and freezing scope all rely on predictive control instead.

Question 29Agile Way of Thinking

A Product Owner is challenged that Agile has no place for documentation. Which response is most accurate?

  1. Agile values working software over comprehensive documentation while still valuing useful documentation. Correct answer.
  2. Agile requires the same documentation as a predictive approach, only written later.
  3. Agile leaves documentation entirely to the Scrum Master's discretion.
  4. Agile forbids documentation because working software is valued instead.

Explanation

The Agile principle values working software over comprehensive documentation, which means documentation is still valued but is not produced for its own sake. It does not forbid documentation, mandate parity with predictive approaches, or assign the decision to the Scrum Master.

Question 30Agile Way of Thinking

A Product Owner is tempted to add a new stakeholder request to the current Sprint to avoid conflict. Which consideration should guide the decision?

  1. The request should be added only if the Scrum Master approves the change.
  2. The Sprint Backlog is fixed, so the request must wait for a future Sprint.
  3. The request may be negotiated with the Developers if it does not endanger the Sprint Goal. Correct answer.
  4. The request may be added if the Product Owner accepts it, because the Product Owner controls scope.

Explanation

Scope may be clarified and renegotiated with the Developers as more is learned, provided the Sprint Goal remains achievable. The Sprint Backlog is not frozen, the Product Owner cannot unilaterally override the team's capacity, and the Scrum Master does not approve scope changes.

Question 31Agile Way of Thinking

A Product Owner wants to apply the Agile principle of welcoming changing requirements. Which behavior best demonstrates that principle?

  1. Rejecting changes during a Sprint and reviewing them only at the next annual planning cycle.
  2. Ordering the Product Backlog so that late-emerging changes can be accommodated in future Sprints. Correct answer.
  3. Accepting every change request immediately, regardless of its effect on the Sprint Goal.
  4. Requiring stakeholders to submit changes only through a formal change control board.

Explanation

Welcoming changing requirements means keeping the backlog ordered and refined so that new insight can be incorporated in upcoming Sprints without destabilizing current work. Accepting every change indiscriminately, deferring changes to an annual cycle, or routing them through a change board all work against that principle.

Question 32Agile Way of Thinking

A Product Owner is deciding how much detail a Product Backlog item needs before the Developers can start work on it. Which approach aligns with Agile thinking?

  1. Items are detailed by the Scrum Master so that the Product Owner can focus on stakeholders.
  2. Items are detailed only after they have been delivered, to document what was built.
  3. Items are detailed just enough and just in time, with the nearest items refined most. Correct answer.
  4. Every item must be fully specified before it can be ordered in the Product Backlog.

Explanation

Progressive refinement keeps the backlog detailed just enough and just in time, concentrating detail on the items most likely to be worked on next. Fully specifying everything up front creates waste, detailing after delivery is too late, and backlog refinement is a Product Owner responsibility shared with the Developers.

Question 33Agile Way of Thinking

A Product Owner is asked how Scrum treats the traditional role of project manager. Which statement is most accurate?

  1. The project manager role is retained but renamed to Scrum Master.
  2. The project manager role is retained but renamed to Product Owner.
  3. The accountabilities are distributed across the Product Owner, Scrum Master, and Developers. Correct answer.
  4. The project manager role is eliminated and its responsibilities are left unassigned.

Explanation

Scrum does not include a project manager accountability; instead, the traditional responsibilities are distributed among the Product Owner, Scrum Master, and Developers. Renaming the role to Scrum Master or Product Owner misstates those accountabilities, and leaving the work unassigned would create a gap.

Question 34Agile Way of Thinking

A Product Owner notices that the team delivers a large batch every quarter with no intermediate feedback. Which action best aligns with Agile thinking?

  1. Reduce batch size so that working increments can be inspected more frequently. Correct answer.
  2. Extend the Sprint length to reduce the overhead of reviews.
  3. Increase the batch size so that fewer releases are needed.
  4. Add a stage gate before each release to improve quality control.

Explanation

Agile thinking favors small batches and frequent delivery of working increments so that feedback arrives sooner and risk is reduced. Larger batches, stage gates, and longer Sprints all delay feedback and increase the cost of change.

Question 35Agile Way of Thinking

A Product Owner is deciding whether to release an Increment that meets the Definition of Done. Which statement reflects Agile thinking about release timing?

  1. An Increment should be released only after the entire Product Goal has been achieved.
  2. Release timing is a technical decision that belongs solely to the Developers.
  3. An Increment must be released at the end of every Sprint to realize value.
  4. Release decisions should be driven by value and risk, not by the mere existence of a Done Increment. Correct answer.

Explanation

A Done Increment is releasable, but whether to release is a value and risk decision that the Product Owner makes with stakeholders. Mandatory release every Sprint, waiting for the whole Product Goal, or delegating the decision entirely to the Developers all misstate that responsibility.

Question 36Agile Way of Thinking

A Product Owner is reviewing how the Scrum values apply to Product Backlog decisions. Which statement is most accurate?

  1. The Scrum values are primarily a tool for performance appraisal of team members.
  2. The Scrum values are optional and apply only when the organization formally adopts them.
  3. The Scrum values apply only to the Developers' technical work.
  4. The Scrum values guide behavior across all Scrum accountabilities, including backlog ordering. Correct answer.

Explanation

The Scrum values of commitment, focus, openness, respect, and courage guide the behavior of everyone involved in Scrum, including the Product Owner when ordering the backlog. They are not limited to technical work, are not optional, and are not intended as an appraisal instrument.

Question 37Agile Way of Thinking

A stakeholder asks the Product Owner why the team does not simply follow the original plan when new information emerges. Which explanation best reflects Agile thinking?

  1. The plan is replaced by the Sprint Backlog, which is the only plan Scrum recognizes.
  2. The plan is discarded entirely because planning has no value in Agile.
  3. The plan is kept because changing it would reduce predictability.
  4. The plan is a forecast that is updated as empirical evidence accumulates. Correct answer.

Explanation

Agile planning treats plans as forecasts that are revised as evidence accumulates, which is how empirical control works. Keeping a plan despite new evidence, discarding planning altogether, or denying that Scrum uses plans all misrepresent Agile thinking.

Question 38Agile Way of Thinking

A Product Owner is asked how Scrum addresses the risk that a large feature will be misunderstood. Which approach best reflects Agile thinking?

  1. Deliver a thin slice of the feature early and use the feedback to refine the rest. Correct answer.
  2. Assign the feature to a single expert who will not be disturbed until it is finished.
  3. Write a complete specification and obtain sign-off before any development begins.
  4. Build the entire feature and validate it with users at the end of the release.

Explanation

Delivering a thin slice early exposes assumptions to real feedback and reduces the cost of being wrong, which is central to Agile risk management. Building everything before validating, relying on up-front sign-off, or isolating a single expert all delay learning and increase risk.

Question 39Agile Way of Thinking

A Product Owner observes that the team is praised for long hours and weekend work. Which response best reflects Agile thinking about sustainable pace?

  1. Accept the pattern as long as the Sprint Goal is met.
  2. Celebrate the effort, because dedication is a core Scrum value.
  3. Reduce the Definition of Done so that less work is required.
  4. Treat the pattern as a warning sign and address the underlying causes of the overload. Correct answer.

Explanation

Agile thinking holds that sustainable pace is necessary for consistent delivery and that chronic overtime signals a systemic problem to be addressed. Celebrating or accepting the pattern, or weakening the Definition of Done, treats a symptom rather than the cause.

Question 40Agile Way of Thinking

A Product Owner is deciding how to handle a stakeholder who wants a detailed commitment for work two years ahead. Which response best reflects Agile thinking?

  1. Offer a forecast with explicit assumptions and commit in detail only to near-term work. Correct answer.
  2. Refuse to discuss future work until the current Sprint is complete.
  3. Provide the detailed commitment, because stakeholders need certainty to plan.
  4. Delegate the commitment to the Developers so that the Product Owner remains flexible.

Explanation

Agile thinking recognizes that long-range detail is unreliable and replaces it with transparent forecasts and near-term commitments that can be adjusted as evidence arrives. Giving false certainty, refusing all discussion, or shifting the commitment to the Developers all undermine trust and empiricism.

Question 41Product Owner role

In Scrum, which statement best captures accountability for maximizing product value?

  1. The Scrum Master is accountable because they remove impediments that block value delivery.
  2. The Developers collectively decide value priorities during Sprint Planning.
  3. The stakeholders are accountable because they fund the product.
  4. The Product Owner is accountable for maximizing value, and may delegate work but not the accountability. Correct answer.

Explanation

Scrum assigns accountability for maximizing product value to the Product Owner, who may delegate tasks to others but cannot transfer the accountability itself. The Scrum Master serves the process, Developers deliver the work, and stakeholders provide input rather than holding this accountability.

Question 42Product Owner role

How many Product Owners does a single Scrum Team have?

  1. Two, one for the business and one for technical quality
  2. As many as the organization needs to represent each function
  3. One, who may delegate tasks but remains the single accountable person Correct answer.
  4. One per stakeholder group that funds the product

Explanation

Each Scrum Team has exactly one Product Owner, ensuring a single clear source of accountability for the Product Backlog. The Product Owner can delegate work to others, but accountability remains with that one person. Multiple owners create conflicting priorities.

Question 43Product Owner role

A Product Owner wants to add a new item to the Product Backlog mid-Sprint. What is the appropriate action?

  1. Wait until the Sprint Review before writing anything down.
  2. Add it to the Product Backlog and let the Developers decide whether and when it enters a Sprint. Correct answer.
  3. Insert it immediately into the current Sprint Backlog to stay responsive.
  4. Ask the Scrum Master to approve the addition before it is recorded.

Explanation

The Product Backlog is a living artifact the Product Owner may update at any time, but the current Sprint's scope is protected. New items are ordered and considered for future Sprints by the Developers during refinement and planning.

Question 44Product Owner role

Which activity is the Product Owner primarily responsible for in Sprint Planning?

  1. Estimating the effort for every backlog item personally
  2. Assigning each task to a specific Developer
  3. Facilitating the meeting and timeboxing the discussion
  4. Explaining the Product Goal and clarifying backlog items so the team can select work Correct answer.

Explanation

In Sprint Planning the Product Owner brings the Product Goal and clarifies items so the Developers can choose what to deliver. Task assignment and estimation belong to the Developers, and facilitation is the Scrum Master's role.

Question 45Product Owner role

What is the primary purpose of the Sprint Review from the Product Owner's perspective?

  1. To inspect the increment with stakeholders and adapt the Product Backlog based on feedback Correct answer.
  2. To approve the budget for the next Sprint
  3. To evaluate individual developer performance
  4. To obtain formal sign-off that closes the project

Explanation

The Sprint Review is a working session where the increment is inspected and stakeholders give feedback that informs backlog adaptation. It is not a sign-off gate, performance review, or budgeting event.

Question 46Product Owner role

A Product Owner keeps a detailed, fully estimated backlog for the next twelve months. What is the main concern?

  1. It prevents the Scrum Master from facilitating Daily Scrums
  2. It violates the rule that backlogs must contain at least 100 items
  3. It removes the need for a Sprint Goal
  4. Excessive upfront detail reduces the ability to adapt as learning occurs Correct answer.

Explanation

Long-range, highly detailed backlogs assume knowledge the team does not yet have and inhibit empiricism. Backlog items should be detailed just in time, with near-term items refined more than distant ones.

Question 47Product Owner role

What does the Product Goal describe?

  1. A future state of the product that serves as a target for the Scrum Team Correct answer.
  2. The definition of quality the increment must meet
  3. The revenue target the Product Owner must reach this quarter
  4. The list of tasks committed to for the current Sprint

Explanation

The Product Goal is a long-term objective describing a future state of the product that guides planning and gives the backlog focus. It is distinct from the Sprint Goal, the Definition of Done, and financial targets.

Question 48Product Owner role

Which ordering approach best reflects Scrum's guidance for the Product Backlog?

  1. Order items by value, risk, dependencies, and learning to maximize outcome Correct answer.
  2. Order strictly by the date each request was received
  3. Order by which stakeholder has the most seniority
  4. Order alphabetically to make items easy to locate

Explanation

The Product Owner orders the backlog to maximize value, considering factors such as value, risk, dependencies, and learning. First-in-first-out, alphabetical, or seniority-based ordering ignores these outcome drivers.

Question 49Product Owner role

How should the Product Owner treat the Definition of Done?

  1. Use it only for regulatory compliance reporting
  2. Redefine it each Sprint to match whatever was completed
  3. Ensure backlog items and acceptance criteria align with it and that increments meet it Correct answer.
  4. Delegate it entirely to stakeholders for approval

Explanation

The Definition of Done is the shared quality standard every increment must meet, and the Product Owner ensures items are transparent against it. It is not redefined to excuse incomplete work or owned solely by stakeholders.

Question 50Product Owner role

A stakeholder bypasses the Product Owner and asks a Developer to prioritize a feature. What should the Product Owner do?

  1. Immediately add the feature to the top of the backlog to avoid conflict
  2. Ask the Scrum Master to remove the stakeholder from future reviews
  3. Reinforce that all backlog requests flow through the Product Owner and evaluate the request on its merits Correct answer.
  4. Report the Developer for insubordination

Explanation

A single ordering authority keeps priorities coherent, so requests should be channeled through the Product Owner, who then evaluates them transparently. Punishing the Developer or excluding stakeholders damages trust and transparency.