Professional Scrum Master I

When many Scrum Teams are working on the same product, all of their Increments should be integrated every Sprint. This ensures that the Product Owner and stakeholders can accurately inspect what has been completed. Integrated Increments provide a complete view of the progress and functionality of the product, which is essential for informed decision making and maintaining a potentially shippable product increment.

In Scrum, only the Product Owner has the authority to cancel a Sprint. This is explicitly stated in the Scrum Guide, which notes that a Sprint can be canceled if the Sprint Goal becomes obsolete. However, the decision to cancel the Sprint rests solely with the Product Owner, and it cannot be canceled by the Development Team. Therefore, the correct answer is that the Development Team cannot cancel a Sprint; only Product Owners hold that authority.

The output from Sprint Planning that provides the Development Team with a target and overarching direction for the Sprint is the Sprint Goal. The Sprint Goal helps to set the focus and provide a shared objective for the team to work towards during the Sprint. It guides the team in making day-to-day decisions and helps them understand the purpose and expectations for the Sprint.

A Development Team should ensure every Increment meets non-functional requirements. Non-functional requirements are part of the Definition of Done, meaning each increment must adhere to these standards to be considered complete and releasable. This ensures a consistent level of quality and performance across all increments.