True or False: Multiple Scrum Teams working on the same product or system all select work
from the same Product Backlog.

1. A. True
2. B. False

Correct Answer: A

When does a Sprint conclude? (choose the best answer)

1. A. When all the tasks are completed by the Developers.
2. B. When the Sprint Retrospective is complete.
3. C. When all Product Backlog items meet their Definition of Done.
4. D. When the Product Owner decides enough has been delivered to meet the Sprint Goal.

Correct Answer: D
A Sprint is a time-boxed period when a Scrum Team works to complete a set amount of work that delivers value to the customer1. A Sprint concludes when the time-box expires, regardless of whether all the tasks, Product Backlog items, or Definition of Done are completed or not23. The Product Owner has the authority to cancel a Sprint if they determine that the Sprint Goal is obsolete or the work done is no longer valuable1. Therefore, the Product Owner decides when enough has been delivered to meet the Sprint Goal, and the Sprint ends accordingly.

How much work is required of the Developers to complete a Product Backlog item selected during the Sprint Planning?
(choose the best answer)

1. A. As much as they can fit into the Sprint, with remaining work deferred to the next Sprint.
2. B. As much as is required to meet the Scrum Team's Definition of Done.
3. C. All development work and at least some testing.
4. D. A proportional amount of time on analysis, design, development, and testing.

Correct Answer: B
✑ The Developers are the people in the Scrum Team who are accountable for creating a “Done” Increment that meets the Definition of Done each Sprint. The Developers are responsible for planning and executing the Sprint Backlog, designing and building the product functionality, testing and improving the product quality, and delivering a potentially releasable Increment. The Developers work closely with the Product Owner to understand and clarify the Product Backlog items, provide feedback and estimates, and suggest improvements and innovations.
✑ The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The Definition of Done is used to assess when work is complete on the product Increment.
✑ The amount of work required of the Developers to complete a Product Backlog item selected during the Sprint Planning depends on the Definition of Done. The Definition of Done may vary from one Scrum Team to another, depending on the context and domain of work. However, it must be consistent within one team. If there are multiple Scrum Teams working on one product, they must share a common Definition of Done. If there is an organizational standard for a Definition of Done, all Scrum Teams must follow it as a minimum.
✑ The Developers must ensure that each Product Backlog item they complete during a Sprint meets the Definition of Done. This means that they must perform all the necessary tasks and activities to deliver a high-quality product functionality that is usable, valuable, and potentially releasable. This may include analysis, design, development, testing, documentation, integration, deployment, or any other aspects that contribute to the quality and usability of the product.
✑ The other options are not valid or relevant measures for the amount of work required of the Developers to complete a Product Backlog item. They are either too vague, arbitrary, or unrealistic. They are:
References:
✑ Scrum Guide: https://www.scrumguides.org/scrum-guide.html
✑ Definition of Done: https://www.scrum.org/resources/what-is-a-definition-of-done
✑ Developers: https://www.scrum.org/resources/what-is-a-developer-in-scrum