01. What two things best help the Product Owner manage the value of a product?
(choose the best two answers)
a) Devising a formula for a neutral calculation of value
b) Setting value on individual Product Backlog items using Value Poker
c) The order of the Product Backlog
d) Validating assumptions of value through frequent releases
02. A Product Owner is entitled to postpone the start of a new Sprint after the conclusion of a previous Sprint for the following reason:
(choose the best answer)
a) The Product Owner has not identified a Sprint Goal.
b) The Quality Assurance department needs more time to make the previous Increment "Done".
c) There is no acceptable reason. A new Sprint starts immediately after the conclusion of the previous Sprint.
d) Not enough Product Backlog items are "Ready".
e) The stakeholders are not happy with the value produced in the previous Sprint.
03. To what extent does technical debt limit the value a Product Owner can get from a product?
(choose the best two answers)
a) The velocity at which new functionality can be created is reduced when you have technical debt.
b) Technical debt causes a greater percentage of the product's budget to be spent on maintenance of the product.
c) Technical debt does not influence the delivery of value.
d) Technical debt is not a Product Owner concern, because technical debt is only an issue for the Development Team.
04. How do timeboxes help the Product Owner and the other members of the Scrum Team validate assumptions, adapt, and maximize the value of their product?
a) At the end of each Sprint when the timebox expires a detailed report with all test cases and test results is available.
b) Timeboxes assure the Product Owner that the Developers will finish all work on the Sprint Backlog by the end of the Sprint.
c) Timeboxes help by making sure a Sprint does not stop until all testing is done, and the work is verified by the Product Owner.
d) Timeboxes help minimize risk by creating the opportunity to validate assumptions using feedback from users and the market; allowing Scrum Teams to inspect progress toward the Product Goal and decide whether to pivot or persevere.
05. The Developers find out during the Sprint that they are not likely to build everything they forecast. What would you expect a Product Owner to do?
(choose the best answer)
a) Re-negotiate the selected Product Backlog items with the Developers.
b) Cancel the Sprint.
c) Change the Sprint Goal.
d) Inform management that more resources are needed.
e) Skip Product Backlog refinement activities.
06. Which description best fits the role of the Product Owner?
a) Scope Protector.
b) Chief Business Analyst.
c) Value Maximizer.
d) Requirements Collector.
e) Project Manager 2.0.
07. What are typical activities for a Product Owner in a Sprint?
(choose the best two answers)
a) Create financial reporting upon the spent hours reported by the Scrum Team.
b) Collaborate with stakeholders, user communities, and subject matter experts.
c) Work with the Developers on Product Backlog refinement.
d) Update the work plan for the Developers on a daily basis.
e) Attend every Daily Scrum to answer functional questions on the discussed Sprint Backlog items.
08. Who ensures that every Development Team member performs their tasks for the Sprint?
a) The Project Manager
b) The Scrum Master
c) The Product Owner
d) The Development Team
09. When can the Product Backlog be updated?
(choose the best answer)
a) Never, unless agreed to by the change request.
b) At any time when done by the Product Owner or a delegate.
c) Only after a Sprint Review if agreed to by the stakeholders.
d) Only during Product Backlog refinement sessions if the Product Owner is present.
10. To create focus which of the following are most important to have ready when Sprint Planning begins?
(choose the best two answers)
a) Formal budget approval to conduct another Sprint.
b) A Product Backlog with the most important items ready for discussion.
c) A clear cadence of when the Daily Scrum will take place.
d) A clear and non-negotiable Sprint Goal.
e) A fully refined Product Backlog.
f) A Product Goal communicated by the Product Owner.