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

EXIN Agile Scrum Product Owner practice questions

One question at a time. Build your EXIN Agile Scrum Product Owner 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

In Scrum, which statement best describes the Product Owner's accountability for value?

  1. The Product Owner maximizes product value and decides how the Scrum Team orders its work. Correct answer.
  2. The Product Owner maximizes product value and shares the ordering decision with the Scrum Master.
  3. The Product Owner maximizes product value and lets the Developers choose the order of backlog items.
  4. The Product Owner maximizes product value and may delegate ordering decisions to stakeholders.

Explanation

Scrum assigns the Product Owner accountability for maximizing value, including how the Product Backlog is ordered. This accountability is not shared with the Scrum Master or delegated to stakeholders, though the Product Owner may consult them. The Developers decide how much they can do, not the order of the backlog.

Question 2Agile Way of Thinking

An organization asks whether Scrum allows a single person to hold both the Product Owner and Scrum Master accountabilities. What does Scrum guidance say?

  1. It is required whenever the team has fewer than five members.
  2. It is discouraged, because the two accountabilities require different focus and can conflict. Correct answer.
  3. It is encouraged, because one person can then remove impediments faster.
  4. It is allowed only during the first Sprint while the team is forming.

Explanation

Scrum guidance discourages combining the Product Owner and Scrum Master accountabilities in one person because each demands a different focus and the combination can create conflicts of interest. The Product Owner focuses on value and backlog ordering, while the Scrum Master focuses on team effectiveness and the Scrum process. Team size does not change this guidance.

Question 3Agile Way of Thinking

Which activity most clearly reflects the empirical principle of inspection in Scrum?

  1. The team reviewing the Increment against the Sprint Goal at the Sprint Review. Correct answer.
  2. The Product Owner writing detailed specifications before the first Sprint begins.
  3. The Scrum Master assigning tasks to Developers each morning.
  4. The stakeholders signing a fixed scope document at project kickoff.

Explanation

Empiricism rests on transparency, inspection, and adaptation, and the Sprint Review is a formal opportunity to inspect the Increment and adapt the backlog. Inspection means frequently examining progress toward agreed goals. Pre-written specifications, task assignment, and fixed scope documents do not create recurring inspection of actual work.

Question 4Agile Way of Thinking

A Product Owner wants to reduce risk when requirements are unclear at the start of a product. Which approach is most consistent with the Agile way of thinking?

  1. Lock the Product Backlog after Sprint 1 so the team is not disturbed.
  2. Postpone all releases until every backlog item is estimated precisely.
  3. Complete a full requirements baseline before any development begins.
  4. Deliver a small usable Increment early and use feedback to refine the Product Backlog. Correct answer.

Explanation

Agile thinking favors early, frequent delivery of valuable increments so that real feedback informs decisions. This reduces risk because assumptions are tested cheaply and early. Baseline-first planning, delayed release, and frozen backlogs all remove the feedback loops that make uncertainty manageable.

Question 5Agile Way of Thinking

Which pairing correctly matches a Scrum event with its primary purpose in the empirical cycle?

  1. Daily Scrum: adapting the Sprint Backlog toward the Sprint Goal. Correct answer.
  2. Sprint Retrospective: demonstrating the Increment to stakeholders.
  3. Sprint Planning: collecting formal sign-off from the sponsor.
  4. Sprint Review: inspecting the team's processes and working agreements.

Explanation

The Daily Scrum lets the Developers inspect progress toward the Sprint Goal and adapt the Sprint Backlog accordingly. Each Scrum event serves a distinct inspection-and-adaptation purpose. Confusing those purposes undermines the transparency Scrum depends on.

Question 6Agile Way of Thinking

A Product Owner keeps a separate detailed requirements document that differs from the Product Backlog. Which Agile principle does this most directly undermine?

  1. Velocity, because the team cannot calculate its Sprint capacity.
  2. Timeboxing, because events may overrun their limits.
  3. Transparency, because decisions rest on artifacts that do not reflect a single source of truth. Correct answer.
  4. Servant leadership, because the Scrum Master loses authority.

Explanation

Empiricism requires transparency: the artifacts used to make decisions must accurately reflect reality. Maintaining a divergent requirements document means stakeholders and the team may act on conflicting information. Velocity, leadership style, and timeboxing are not the primary principle at stake here.

Question 7Agile Way of Thinking

Which statement best captures the Agile view of working software or a usable Increment over comprehensive documentation?

  1. Documentation replaces the need for a Sprint Review because it records decisions.
  2. Documentation must be completed for each backlog item before the item is demonstrated.
  3. Documentation is valuable when it supports the product, but a usable Increment is the primary measure of progress. Correct answer.
  4. Documentation has no place in Scrum and should be eliminated.

Explanation

The Agile preference for working software over comprehensive documentation is a matter of relative value, not a ban on documentation. A usable Increment provides the clearest evidence of progress, while documentation remains useful where it adds value. Scrum does not require documentation per item or as a substitute for review.

Question 8Agile Way of Thinking

A stakeholder asks the Product Owner to add a high-value item mid-Sprint that would replace work already underway. What is the most Scrum-consistent response?

  1. Ask the Scrum Master to decide whether the change enters the Sprint.
  2. Negotiate the change with the Developers and, if needed, plan it for the next Sprint. Correct answer.
  3. Reject all changes until the product is released to protect the Sprint.
  4. Add the item to the Sprint Backlog and remove an equivalent amount of work immediately.

Explanation

During a Sprint the Sprint Goal should remain stable, and scope may be clarified and renegotiated between the Product Owner and the Developers. New high-value items are normally ordered in the Product Backlog and taken up in a later Sprint. Unilateral insertion or a blanket refusal both ignore the collaboration Scrum expects.

Question 9Agile Way of Thinking

How does the Product Owner role differ from a traditional project manager in an Agile way of thinking?

  1. The Product Owner controls the team's daily schedule and approves individual work hours.
  2. The Product Owner produces the detailed work breakdown and assigns each task to a developer.
  3. The Product Owner owns the budget and signs off on each developer's deliverables.
  4. The Product Owner focuses on maximizing value and ordering the backlog rather than directing tasks and schedules. Correct answer.

Explanation

The Product Owner is value-oriented, deciding what is most worth building and in what order. A traditional project manager typically coordinates tasks, schedules, and individual assignments. In Scrum the Developers self-manage their work, so task direction and hour control do not belong to the Product Owner.

Question 10Agile Way of Thinking

Which behavior best demonstrates the Scrum value of respect within a Scrum Team?

  1. The Product Owner accepting that Developers are the experts on how to create the Increment. Correct answer.
  2. The Developers deferring all backlog ordering questions to the Product Owner without discussion.
  3. The Scrum Master approving technical design choices before implementation.
  4. The team avoiding disagreement in reviews to keep meetings pleasant.

Explanation

Respect in Scrum includes recognizing that the Developers are accountable for the technical how, while the Product Owner is accountable for value and ordering. This mutual recognition lets each role contribute its expertise. Approval of design by the Scrum Master or silencing disagreement works against respect and openness.

Question 11Agile Way of Thinking

A team delivers a valuable Increment but repeatedly misses its Sprint Goal because it overcommits. Which empirical response fits Scrum best?

  1. The Product Owner reduces the number of items selected in Sprint Planning based on observed capacity. Correct answer.
  2. The Product Owner removes the Sprint Goal so the team cannot miss it.
  3. The Scrum Master adds overtime so the team can meet the original commitment.
  4. The Developers stop estimating and accept all incoming requests.

Explanation

Empiricism calls for adapting based on what inspection reveals; persistent overcommitment signals that selection is misaligned with capacity. Adjusting how much work is selected at Sprint Planning is a direct, evidence-based adaptation. Overtime, removing the goal, and abandoning estimation all avoid the underlying issue.

Question 12Agile Way of Thinking

Which statement about the Product Owner and the Sprint Review is correct?

  1. The Product Owner uses the review to assign action items to individual stakeholders.
  2. The Product Owner presents a status report and asks stakeholders to approve the release plan.
  3. The Product Owner leaves the review to the Developers because value is their concern.
  4. The Product Owner explains what backlog items were done and not done, and discusses progress toward the Product Goal. Correct answer.

Explanation

At the Sprint Review the Product Owner communicates what was and was not completed and how that relates to the Product Goal. The event is a working session to inspect the Increment and adapt the Product Backlog with stakeholders. It is not a status sign-off meeting, and the Product Owner does not delegate the value discussion entirely.

Question 13Agile Way of Thinking

A product has a clear long-term direction, but the exact features are still uncertain. How should the Product Owner express this in the Product Backlog?

  1. Record only the next Sprint's items and ignore the longer-term direction.
  2. Keep items coarse where uncertainty is high and refine them as more is learned. Correct answer.
  3. Convert the direction into a fixed contract with dates for each feature.
  4. Write every requirement in final detail so the team is never blocked.

Explanation

Backlog refinement is progressive: items likely to be worked on soon are made small and clear, while distant items can stay coarse. This matches the Agile acceptance of emerging requirements. Detailing everything upfront or ignoring direction both reduce the ability to adapt.

Question 14Agile Way of Thinking

Which statement correctly reflects the Agile Manifesto's preference regarding customer collaboration?

  1. Contract negotiation must be eliminated from all supplier relationships.
  2. Customer collaboration is valued more highly than contract negotiation. Correct answer.
  3. Customer collaboration applies only after the product is released.
  4. Contract negotiation is valued more highly than customer collaboration.

Explanation

The Agile Manifesto states that customer collaboration is valued over contract negotiation, while still recognizing value in negotiation. The preference concerns relative emphasis, not elimination. Collaboration is continuous throughout development, not something that begins after release.

Question 15Agile Way of Thinking

A Product Owner faces pressure to promise a fixed set of features by a fixed date for a complex new product. Which response best reflects Agile thinking?

  1. Fix the date and team, keep scope flexible, and forecast based on empirical data. Correct answer.
  2. Commit to a fixed scope and date, then use overtime to protect the promise.
  3. Promise every feature but hide the uncertainty from stakeholders until the last Sprint.
  4. Refuse to give stakeholders any forecast until all requirements are fully known.

Explanation

In complex work the reliable approach is to fix time and capacity while letting scope emerge, using observed data to forecast. Committing to fixed scope and date assumes predictability that complex product development does not have. Transparency about uncertainty allows stakeholders to make informed decisions.

Question 16Agile Way of Thinking

Which phrase best describes how the Product Owner is expected to treat the Product Backlog over time?

  1. As a temporary list discarded after each Sprint and rebuilt from scratch.
  2. As a private document owned by the Product Owner and hidden from the Developers.
  3. As a continuously evolving artifact that is refined as understanding grows. Correct answer.
  4. As a fixed list frozen at project approval and changed only by formal change requests.

Explanation

The Product Backlog is a living artifact that emerges and is refined as the product and its context change. It is visible to the Scrum Team and provides transparency about upcoming work. Freezing it, hiding it, or discarding it each Sprint removes that transparency and adaptability.

Question 17Agile Way of Thinking

A Product Owner discovers that a competitor released a feature that makes a planned backlog item far less valuable. What is the most appropriate action?

  1. Order the backlog to reflect the new value assessment and discuss the change with the team. Correct answer.
  2. Remove the item silently so no one notices the change in direction.
  3. Keep the item in its original position to avoid disrupting the team.
  4. Ask the Developers to decide the item's priority because they build it.

Explanation

The Product Owner is accountable for maximizing value, which includes reordering the backlog when new information changes relative value. Discussing the change with the team keeps transparency and allows planning to adapt. Ignoring new information, delegating priority, or acting silently all undermine the role and transparency.

Question 18Agile Way of Thinking

Which statement best describes how the Product Goal relates to the Product Backlog?

  1. The Product Goal is a fixed deadline set by the sponsor at project approval.
  2. The Product Goal is a long-term objective for the product that the Product Backlog helps to fulfill. Correct answer.
  3. The Product Goal is a list of every task required to complete the current Sprint.
  4. The Product Goal is a metric that the Developers must meet in each Daily Scrum.

Explanation

The Product Goal describes a future state of the product that serves as a target for the Scrum Team. The Product Backlog is ordered toward achieving it and is refined as understanding grows. It is not a task list, a sponsor deadline, or a daily metric.

Question 19Agile Way of Thinking

A Scrum Team must choose between two backlog items of similar size. Item A delivers learning that could change the product direction; item B delivers a modest, certain improvement. Which ordering best reflects Agile thinking about uncertainty?

  1. Defer both until the product direction is fully known.
  2. Order item B first because certain value always outranks uncertain value.
  3. Order them alphabetically so the team cannot be accused of bias.
  4. Order item A first because early learning can reduce larger downstream risk. Correct answer.

Explanation

Agile thinking treats learning as a way to reduce risk, so items that resolve important uncertainty can be worth doing early even when their direct value is less certain. Certain small improvements are valuable but do not address the larger risk. Arbitrary ordering and indefinite deferral avoid the decision rather than making it.

Question 20Agile Way of Thinking

Which statement best describes self-managing teams in Scrum?

  1. The Product Owner assigns each task daily to balance the workload.
  2. Stakeholders approve each developer's daily plan before work starts.
  3. The Developers decide internally who does what, when, and how to produce the Increment. Correct answer.
  4. The Scrum Master sets the technical standards the team must follow.

Explanation

Scrum teams are self-managing, meaning the Developers determine how to turn backlog items into a valuable Increment, including internal task allocation. This autonomy supports ownership and fast decisions. Daily assignment by the Product Owner, imposed standards, or external approval of daily plans all contradict self-management.

Question 21Agile Way of Thinking

A Product Owner is tempted to measure success mainly by how many story points the team completes each Sprint. Why is this a weak Agile measure?

  1. It is invalid because story points can never be counted.
  2. It measures output volume rather than the value delivered to customers and users. Correct answer.
  3. It is weak because value can only be measured after the product is retired.
  4. It is weak because velocity should be reported only to the Scrum Master.

Explanation

Story points estimate relative effort, so counting them measures activity rather than the value created. Agile thinking focuses on outcomes such as customer and business value, not raw output. Points can be counted, velocity is useful for forecasting, and value is observable well before retirement.

Question 22Agile Way of Thinking

What does the Agile principle about simplicity most directly encourage a Product Owner to do?

  1. Require the team to document every alternative considered.
  2. Increase the number of features in each Sprint to show progress.
  3. Maximize the amount of work not done by eliminating low-value backlog items and steps. Correct answer.
  4. Add more detailed process steps so nothing is overlooked.

Explanation

Simplicity, defined as maximizing the amount of work not done, directs the Product Owner to cut low-value items and unnecessary steps. This focuses effort on what matters most. Adding process, inflating scope, and documenting every alternative all increase work without increasing value.

Question 23Agile Way of Thinking

A team's stakeholders keep bypassing the Product Owner and giving requests directly to individual Developers. What is the most appropriate Product Owner response?

  1. Work with stakeholders to route requests into the Product Backlog and explain why this helps them. Correct answer.
  2. Ask the Scrum Master to punish stakeholders who bypass the process.
  3. Instruct the Developers to refuse all contact with stakeholders from now on.
  4. Accept that priorities will now be set by whichever stakeholder speaks first.

Explanation

The Product Owner protects focus by making the Product Backlog the single entry point for requests, while keeping stakeholders engaged. Explaining the benefit helps stakeholders see why this serves their interests. Cutting off contact, letting the loudest voice set priorities, or punitive action all damage collaboration.

Question 24Agile Way of Thinking

Which statement best explains why Scrum favors cross-functional teams?

  1. The team has all the skills needed to create a valuable Increment without depending on outside handoffs. Correct answer.
  2. Each team member is expected to master every skill the product requires.
  3. Cross-functionality means the team includes representatives from every stakeholder group.
  4. Cross-functional teams remove the need for a Product Owner.

Explanation

Cross-functional means the team collectively holds the skills needed to deliver a valuable Increment, reducing dependency and handoff delays. It does not require every individual to master every skill. Cross-functionality concerns skills, not stakeholder representation, and does not eliminate any accountability.

Question 25Agile Way of Thinking

A Product Owner wants to shorten feedback loops across several Sprints. Which practice is most consistent with Agile thinking?

  1. Keep the Increment internal until every planned feature is complete.
  2. Release a usable Increment frequently and gather user feedback to inform the next Sprint. Correct answer.
  3. Run one large release at the end of the program to avoid partial features.
  4. Collect feedback only through an annual satisfaction survey.

Explanation

Frequent delivery of a usable Increment is the Agile mechanism for shortening feedback loops and validating assumptions with real users. Feedback gathered early can shape the backlog while change is still inexpensive. A single large release, annual surveys, and withholding the Increment all extend the loop.

Question 26Agile Way of Thinking

In the Agile way of thinking, what is the primary purpose of delivering a usable Increment at the end of every Sprint?

  1. To satisfy the documentation requirements of the quality department
  2. To enable early and continuous feedback from stakeholders on real working product Correct answer.
  3. To allow management to compare team velocity against other teams
  4. To prove that every Developer completed their assigned tasks on time

Explanation

Agile thinking values working software as the main measure of progress, so a usable Increment exists to generate real feedback early and often. That feedback lets the Product Owner inspect value and adapt the Product Backlog based on evidence rather than assumptions.

Question 27Agile Way of Thinking

A Product Owner is deciding how much detail to put into Product Backlog items that will not be worked on for several months. Which approach best reflects Agile thinking?

  1. Assign each one a fixed Sprint number in advance
  2. Describe them in fine detail now so that nothing is forgotten later
  3. Keep them coarse and refine them progressively as they move closer to being built Correct answer.
  4. Remove them entirely until a full specification can be written

Explanation

Agile planning is progressive, so distant items are kept at a low level of detail and elaborated just in time. This avoids wasted effort on details that will likely change before the work begins.

Question 28Agile Way of Thinking

Which statement best captures the Agile attitude toward responding to change?

  1. Plans should be avoided because they are always wrong
  2. Change is discouraged once the Sprint has started
  3. Responding to change is valued over following a plan Correct answer.
  4. Change is accepted only after a formal change-control board approves it

Explanation

The Agile Manifesto values responding to change over following a plan, which means plans are useful but not rigid. The intent is to welcome changing requirements that improve the product, even late in development.

Question 29Agile Way of Thinking

A stakeholder asks the Product Owner why the Scrum Team is not organized into separate analysis, development, and testing departments. Which answer best reflects Agile thinking?

  1. Cross-functional teams can deliver a complete Increment without depending on other groups Correct answer.
  2. Testing departments should report to the Product Owner
  3. Specialist departments are prohibited by the Scrum Guide
  4. Separate departments always produce lower quality code

Explanation

Cross-functional teams hold all the skills needed to create value, which shortens handoffs and lets them deliver a Done Increment independently. This supports faster feedback and greater self-management.

Question 30Agile Way of Thinking

A Product Owner learns that a regulatory change will make one planned feature mandatory within two Sprints. What is the most Agile response?

  1. Re-order the Product Backlog to reflect the new value and risk, and let the team plan it at the next Sprint Planning Correct answer.
  2. Add the feature to the current Sprint and drop the Sprint Goal
  3. Wait until the original roadmap is complete before considering the change
  4. Ask the team to work overtime so both the original scope and the new feature fit

Explanation

The Product Backlog is ordered by value, risk, and necessity, so a mandatory change justifies re-ordering it. The Scrum Team then decides during Sprint Planning how to address it while protecting the current Sprint Goal.

Question 31Agile Way of Thinking

Two backlog items have similar value. Item A is well understood, while Item B carries major technical and market uncertainty. How should the Product Owner most likely order them?

  1. Item A first, because predictable work is safer
  2. Item B first, because uncertainty should be reduced early Correct answer.
  3. Alphabetically, to keep the backlog neutral
  4. Whichever the Developers prefer, since ordering is their decision

Explanation

Agile thinking favors reducing uncertainty early so that expensive decisions are based on evidence. Bringing the risky item forward generates learning that can reshape the rest of the backlog.

Question 32Agile Way of Thinking

A Product Owner wants to measure whether the product is actually delivering value. Which measure is most consistent with Agile thinking?

  1. The count of backlog items closed since project start
  2. Evidence of customer usage and outcome achieved against the Product Goal Correct answer.
  3. The number of hours the team logged this Sprint
  4. The percentage of planned story points completed

Explanation

Agile thinking focuses on outcomes and value rather than output volume. Customer usage and progress toward the Product Goal show whether the Increment actually solved a problem.

Question 33Agile Way of Thinking

A Product Owner insists on approving every design decision the Developers make. Which Agile principle does this most directly undermine?

  1. The team should maintain a constant velocity
  2. The team should deliver documentation for every decision
  3. The team should be self-managing and trusted to decide how to do its work Correct answer.
  4. The team should avoid contact with stakeholders

Explanation

Agile thinking gives the people doing the work the authority to decide how to do it, and the Product Owner focuses on what and why. Micromanaging design decisions removes ownership and slows the team down.

Question 34Agile Way of Thinking

Which statement best describes how Agile thinking treats a plan created at the start of a product effort?

  1. The plan is unnecessary once the first Sprint begins
  2. The plan must be approved by every stakeholder before each Sprint
  3. The plan is a contract that must be delivered exactly as written
  4. The plan is a forecast that is revised as new information emerges Correct answer.

Explanation

In Agile thinking a plan is a useful forecast that is expected to be updated as learning accumulates. Responding to change is valued over rigidly following the original plan.

Question 35Agile Way of Thinking

A Product Owner is asked to sign off on a detailed five-year feature roadmap for a product with high market uncertainty. What is the most Agile response?

  1. Replace the roadmap with a clear Product Goal and a near-term ordered backlog Correct answer.
  2. Refuse to provide any direction until the market stabilizes
  3. Commit to the full roadmap but label it confidential
  4. Produce the roadmap but hide it from the Developers

Explanation

Agile thinking favors a clear direction expressed as a Product Goal, with detail emerging through an ordered backlog. Long-range certainty is not promised where the market is genuinely uncertain.

Question 36Agile Way of Thinking

Which behavior best illustrates the Agile value of openness within a Scrum Team?

  1. The Developers report only completed work and omit impediments
  2. The Product Owner keeps the backlog private to avoid interference
  3. The Product Owner shares progress, risks, and bad news with stakeholders as soon as they are known Correct answer.
  4. The team shares information only through formal status reports

Explanation

Openness means making the true state of the work and the product visible, including problems. Early disclosure lets stakeholders and the team adapt before small issues become expensive.

Question 37Agile Way of Thinking

A Scrum Team is deciding whether to spend a Sprint building a thin slice of a feature that real users can try, or building the full data model first. Which choice best reflects Agile thinking?

  1. Defer the decision until the annual budget cycle
  2. Build both in parallel to save calendar time
  3. Build the full data model first so later work is not reworked
  4. Build the thin slice to obtain real user feedback before investing further Correct answer.

Explanation

Agile thinking prefers early, real feedback so that investment follows evidence of value. A thin slice tests the riskiest assumptions before large effort is committed.

Question 38Agile Way of Thinking

A Product Owner notices that the team has stopped refining backlog items because the top of the backlog is already detailed. What risk does this create for Agile thinking?

  1. The team will exceed the Sprint timebox
  2. The Definition of Done will become invalid
  3. None, since the top items are the only ones that matter
  4. The backlog may become unable to reflect new learning, weakening its role as a living plan Correct answer.

Explanation

The Product Backlog is a living artifact that must evolve as the product and market change. If refinement stops, the backlog stops reflecting current value and the team loses the ability to adapt quickly.

Question 39Agile Way of Thinking

A Product Owner is under pressure to accept an Increment that does not meet the Definition of Done so that the Sprint can be declared successful. What does Agile thinking require?

  1. Accept it if the missing work is only documentation
  2. Accept it and let the Developers fix it in a later release
  3. Accept it and record the gaps in a risk register
  4. Do not treat it as Done; the Increment is not releasable until it meets the Definition of Done Correct answer.

Explanation

The Definition of Done is the shared quality standard, and work that does not meet it is not an Increment. Accepting incomplete work hides undone effort and undermines transparency and empiricism.

Question 40Agile Way of Thinking

An organization wants to compare Scrum Teams by rewarding the team with the highest story-point total each quarter. Why does this conflict with Agile thinking?

  1. The reward encourages inflating estimates and local output rather than delivering value Correct answer.
  2. Agile forbids the use of any metric in a Sprint Review
  3. Story points should only be counted by the Product Owner
  4. Story points are only valid for teams using the same estimation scale

Explanation

Story points are relative estimates for a single team's planning, not a performance measure across teams. Rewarding point totals invites estimate inflation and shifts focus from customer value to output.

Question 41Product Owner role

In Scrum, which artifact does the Product Owner primarily use to communicate and order the work needed to deliver a product increment?

  1. The Sprint Burndown Chart
  2. The Product Backlog Correct answer.
  3. The team's velocity report
  4. The Definition of Done

Explanation

The Product Backlog is the single ordered list of everything that might be needed in the product, and the Product Owner is accountable for its content, availability and ordering. Other Scrum artifacts and charts serve transparency or quality purposes but are not the PO's ordering tool.

Question 42Product Owner role

Which responsibility belongs to the Product Owner rather than to the Scrum Master?

  1. Maximizing the value delivered by the Development Team's work Correct answer.
  2. Facilitating Scrum events as requested or needed
  3. Removing impediments that block the Development Team
  4. Coaching the organization in adopting Scrum

Explanation

The Product Owner is accountable for maximizing the value of the product resulting from the work of the Development Team. Coaching the organization, removing impediments and facilitating events are Scrum Master accountabilities.

Question 43Product Owner role

A Product Owner wants to delegate the ordering of the Product Backlog to a senior developer while keeping accountability for the result. What does Scrum allow?

  1. Delegation is allowed only if the Scrum Master approves the new ordering
  2. The PO may delegate work but remains accountable for the Product Backlog and its ordering Correct answer.
  3. Accountability transfers to the developer once the ordering is delegated
  4. Delegation is forbidden because the PO must personally write every item

Explanation

Scrum allows the Product Owner to delegate tasks and responsibilities, but accountability for the Product Backlog, including its ordering, cannot be transferred away. The PO stays answerable for the outcome even when others do the ordering work.

Question 44Product Owner role

The Development Team tells the Product Owner that a backlog item cannot be finished within the current Sprint because it is larger than expected. What is the most appropriate PO response?

  1. Ask the Scrum Master to change the Sprint Goal so the item fits
  2. Instruct the Development Team to work overtime so the original scope is met
  3. Negotiate the scope of the Sprint with the Development Team while protecting the Sprint Goal Correct answer.
  4. Add the remaining work to the next Sprint and extend the current Sprint by a few days

Explanation

Scope may be clarified and renegotiated with the Development Team as more is learned, provided the Sprint Goal is not endangered. Sprint length is fixed and cannot be extended, and the PO does not direct how the team does its work.

Question 45Product Owner role

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

  1. To obtain formal sign-off that freezes the backlog for the next release
  2. To inspect the increment with stakeholders and adapt the Product Backlog based on feedback Correct answer.
  3. To demonstrate individual developer performance to management
  4. To let the Scrum Master report team velocity to the steering committee

Explanation

The Sprint Review is a working session where the increment is inspected and the Product Backlog is adapted to reflect what was learned. It is a collaborative inspection of the product, not a performance appraisal or a sign-off gate.

Question 46Product Owner role

A Product Owner is preparing for Sprint Planning. Which input is most relevant for proposing a Sprint Goal?

  1. The complete list of defects reported by the support desk
  2. The organizational chart of the stakeholder community
  3. The salary bands of the Development Team members
  4. The ordered Product Backlog and the team's past performance Correct answer.

Explanation

Sprint Planning starts from the ordered Product Backlog and what the team has learned about its capacity and past performance. The PO uses this to propose a Sprint Goal that delivers value.

Question 47Product Owner role

Which statement best describes how a Product Owner should treat the Product Backlog over time?

  1. It is maintained exclusively by the Scrum Master on the PO's behalf
  2. It is rebuilt from scratch at the beginning of every Sprint
  3. It is baselined at project start and changed only through formal change requests
  4. It is continuously refined and reordered as understanding of the product grows Correct answer.

Explanation

The Product Backlog is a living artifact that is refined and reordered continuously as the product, market and team understanding evolve. Baselining or rebuilding it each Sprint contradicts its emergent nature.

Question 48Product Owner role

What does the Product Owner primarily use to express the size of Product Backlog items relative to each other?

  1. The monetary budget allocated to each item
  2. Relative estimation agreed with the Development Team Correct answer.
  3. The number of lines of code each item requires
  4. Absolute effort in person-hours fixed by the PO

Explanation

Backlog items are typically sized using relative estimation, and the Development Team is responsible for the estimates. The PO may facilitate but does not impose absolute effort figures.

Question 49Product Owner role

A stakeholder repeatedly bypasses the Product Owner and asks developers to add features mid-Sprint. What should the Product Owner do?

  1. Allow the developers to accept the request if it is small enough
  2. Add the feature immediately and let the team decide when to build it
  3. Ask the Scrum Master to ban the stakeholder from future Sprint Reviews
  4. Reinforce that all product requests flow through the Product Backlog and the PO's ordering Correct answer.

Explanation

The Product Owner is the single point of contact for product requirements, and requests should enter through the Product Backlog to be ordered against other work. Letting developers accept ad hoc requests undermines the Sprint and the PO's accountability.

Question 50Product Owner role

Which description matches a good Sprint Goal as the Product Owner would frame it?

  1. A copy of the release plan with dates assigned to each backlog item
  2. A detailed list of every task each developer must complete that Sprint
  3. A commitment to deliver a fixed set of story points regardless of content
  4. A short statement of the value the Sprint should deliver, giving the team flexibility on how to achieve it Correct answer.

Explanation

The Sprint Goal expresses why the Sprint is valuable and provides coherence, while leaving the team room to negotiate how the work is done. It is not a task list, a points target or a dated release plan.