01. A department head is unhappy that a feature they requested sits low in the Product Backlog. They ask the Developers to work on it during the next Sprint without telling the Product Owner.
What should the Developers do?
a) Decline, and direct the department head to the Product Owner to make their case.
b) Take the work, since the Developers are self-managing and choose how to spend the Sprint.
c) Refer it to the Scrum Master to decide whether it is important enough.
d) Take the work if it fits alongside the Sprint Goal without extending the Sprint.
02. A Product Backlog contains new features, a growing set of defects, and technical work the Developers say is needed to keep the product changeable. A manager proposes keeping the defects and technical work in a separate list so the Product Backlog shows only customer-visible value.
Which response is best, and why?
a) Use the separate list, pull from it whenever the Developers have spare capacity, and review it each quarter.
b) Keep them in the one Product Backlog, ordered against the features, because all of it is work needed to improve the product and a single ordered list is what makes the trade-off visible.
c) Keep them in the Product Backlog, but order all defects above all features.
d) Use the separate list, but have the Product Owner review it at each Sprint Review.
03. A product has many stakeholders: end users, a compliance team, a support desk, and two downstream teams that consume its output.
How are those competing needs meant to be reflected in Scrum?
a) Each group is given a fixed share of every Sprint's capacity, agreed in advance.
b) The Developers balance the needs while ordering the Product Backlog each Sprint.
c) The Product Owner represents their needs in the Product Backlog.
d) Each stakeholder group maintains its own section of the Product Backlog.
04. A Product Owner maintains the Product Backlog in a private spreadsheet and circulates a summary before each Sprint Planning. Items are worded as short internal shorthand that only the Product Owner fully understands. The Developers routinely discover during a Sprint that an item meant something other than what they assumed, and stakeholders have twice been surprised by what was built.
Which analysis best explains what is going wrong?
a) The Scrum Team is missing a Definition of Ready to gate items into the Sprint.
b) The Product Backlog has low transparency, so decisions made from it are based on a partial view and carry more risk.
c) The Product Owner is failing to delegate Product Backlog management to the Developers.
d) The Developers are not asking enough questions during Sprint Planning, so the fix is to lengthen Sprint Planning and add a written hand-over step.
05. A Scrum Master proposes that the Scrum Team hold a mandatory ninety-minute Product Backlog refinement meeting every Wednesday, and adds it to the calendar as a sixth Scrum event.
What is wrong with this proposal?
a) The Scrum Master may not propose changes to how the Scrum Team works, and may only observe or advise.
b) Scrum prescribes no cadence and no time-box for refinement, so neither the weekly slot nor the ninety minutes can be presented as a requirement.
c) Ninety minutes exceeds the time-box the Scrum Guide sets for refinement, which is sixty minutes per Sprint.
d) Refinement should be attended only by the Product Owner and one Developer.
06. A Scrum Team is describing its artifacts to a new joiner. It says that the Sprint Backlog's commitment is the Definition of Done.
What is wrong with that description?
a) Nothing — the Definition of Done is what the Developers commit to when they plan the Sprint.\
b) The Sprint Backlog's commitment is the Sprint Goal, and the Definition of Done is the commitment for the Increment.
c) The Sprint Backlog's commitment is the Product Goal, because every Sprint serves it.
d) The Sprint Backlog has no commitment of its own, since only the Product Backlog and the Increment carry one that the Scrum Team can measure against.
07. An organization appoints three people to share the Product Owner accountability for one product, each covering a different set of stakeholders.
What does the Scrum Guide say about this?
a) The Product Owner is always one person, not a committee.
b) It is permitted only if a Scrum Master facilitates their decisions.
c) Scrum allows it where the three agree a single ordering of the Product Backlog.
d) It is permitted where a product serves several distinct, well-separated stakeholder groups.
08. At the end of a Sprint, a Product Backlog item is functionally complete but has not been through the security review that the Definition of Done requires. The Product Owner would like to show it to stakeholders at the Sprint Review as finished work.
What should happen?
a) It can be presented as Done because the Product Owner decides what is releasable.
b) It is not part of the Increment and cannot be presented as Done, because only work meeting the Definition of Done is part of an Increment.
c) Stakeholders may accept it as Done at the Sprint Review if they are satisfied with what they see.
d) It can be presented as Done, marked provisional, and re-checked at the next Sprint Review once the outstanding security review has been completed.
09. During a Sprint, a Product Owner re-orders the Product Backlog several times as new market information arrives. A Developer objects that this destabilizes the Sprint.
Who is right?
a) The Developer, because the Product Backlog is frozen once Sprint Planning has ended.
b) The Developer, because re-ordering the Product Backlog is permitted only at the Sprint Review or during the next Sprint Planning.
c) The Product Owner, but only where the Scrum Master has approved each change to the order.
d) The Product Owner, because the Product Backlog may be re-ordered at any time and doing so does not change the Sprint Backlog.
10. Three Scrum Teams work on one product, under one Product Owner. A stakeholder, finding the Product Owner slow to respond, begins approaching each team's Developers directly with requests, and each team has started keeping an informal list of what that stakeholder asked them for.
What is the most significant consequence?
a) Three informal lists now hold work that is ordered against nothing, so the single Product Backlog no longer shows what is most valuable next for the product.
b) Each team needs its own Product Owner so requests can be answered faster.
c) The Product Owner accountability has effectively been divided between the three teams.
d) The teams will duplicate each other's work, because the same request can reach more than one of them and each will size, schedule and build it separately without noticing.