When is a Sprint over? A. When the Product Owner says it is done. B. When all Product Backlog items meet their definition of “Done”. C. When all the tasks are completed. D. When the time-box expires.

How should a Development Team deal with non-functional requirements? A. Ensure every Increment meets them. B. Make sure the release department understands these requirements, but it is not the Development Team’s responsibility. C. Handle them during the Integration Sprint preceding the Release Sprint. D. Assign them to the lead developers on the team.

Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint? A. The Sprint Backlog. B. The Sprint Goal C. The release plan. D. Sprint Review minutes.

When can a Development Team cancel a Sprint? A. It can’t. Only Product Owners can cancel Sprints. B. When functional expectations are not well understood. C. When the Product Owner is absent too often. D. When the selected Product Backlog items for the Sprint become unachievable. E. When a technical dependency cannot be resolved.

When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint? A. Yes, but only for Scrum Teams whose work has dependencies. B. Yes, otherwise the Product Owners (and stakeholders) may not be able to accurately inspect what is done. C. No, each Scrum Team stands alone. […]