Last Attempt PSM-I Questions

The best answer is B. The need for the team to learn based on doing work and measuring results.

The Sprint length should be chosen based on the complexity and volatility of the product and the environment, as well as the team’s capability and Definition of Done. The Sprint length should enable the team to deliver a usable Increment of value that meets the feedback needs of the stakeholders and the business. The Sprint length should also allow the team to inspect and adapt their work processes and practices based on the outcomes of the Sprint.

The other options are not valid reasons for choosing the Sprint length. The organization’s mandate, team formation, and release schedule should not dictate the Sprint length, but rather be aligned with it. The Scrum Team should have the autonomy to choose the Sprint length that best suits their product and context.

You can learn more about how to choose the right Sprint length from these sources: How Long A Sprint Should Be?, How to Choose the Right Sprint Length in Scrum, What is a Sprint?, Determining the Sprint Length, and Sprint Length: What’s the Right Length?.

According to the Scrum Guide, an Increment does not have to be released to customers or users at the end of each Sprint. However, it must be in a usable condition and meet the Definition of Done. The decision to release an Increment is made by the Product Owner, based on the value and feedback obtained from stakeholders. The other option is not valid, as it implies that releasing an Increment is mandatory at the end of each Sprint.

The Developers determine how many Product Backlog items they select for a Sprint, as stated in the Scrum Guide: “The Developers select items from the Product Backlog to include in the current Sprint. The Scrum Team may refine these items during this process, which increases understanding and confidence.”

According to the Scrum Guide1, the Sprint Backlog is the property of the Developers and no one else can tell them which items they should work on. The Developers can select any item from the Product Backlog that they forecast they can complete within a Sprint. The Developers are self-organizing and decide how to turn Product Backlog items into an Increment of value. Therefore, no one owns a Sprint Backlog item, but the entire Development Team is accountable for it.

References: Scrum Guide