When many Scrum Teams are working on the same product, should all of their increments be integrated every Sprint?
The correct answer is B, because the Scrum Guide states that ''at the end of a Sprint, the new Increment must be 'Done,' which means it must be in useable condition and meet the Scrum Team's definition of 'Done'. An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint. The increment is a step toward a vision or goal.'' Therefore, all the increments from different Scrum Teams working on the same product should be integrated every Sprint to enable inspection and adaptation by the Product Owner and stakeholders.
When can a Development Team cancel a Sprint?
The correct answer is A, because the Scrum Guide states that ''a Sprint can be cancelled before the Sprint time-box is over. Only the Product Owner has the authority to cancel the Sprint, although he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.'' Therefore, a Development Team cannot cancel a Sprint by itself.
Which output from Sprint Planning provides the Development Team with a target and overarching direction for the Sprint?
The correct answer is B, because the Scrum Guide states that ''the Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment.'' Therefore, the Sprint Goal provides the Development Team with a target and overarching direction for the Sprint.
How should a Development Team deal with non-functional requirements?
The correct answer is A, because the Scrum Guide states that ''the definition of 'Done' is a formal description of the state of the Increment when it meets the quality measures required for the product.'' Therefore, non-functional requirements should be part of the definition of 'Done' and ensure every Increment meets them.
When is a Sprint over?
The correct answer is D, because the Scrum Guide states that ''a Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.'' Therefore, a Sprint is over when its time-box expires, regardless of whether all Product Backlog items or tasks are completed or not.
