Scrum Updated PSM-I Exam Questions and Answers by ciaran

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?.

 The Scrum Master should be concerned about the ability of the Development Teams to produce integrated Increments, as this is one of the goals of Scrum. The Scrum Master should also encourage the Development Teams to figure out a solution for themselves, as this fosters self-management and collaboration. The other options are not relevant or important for the Scrum Master in this situation.

The best two answers are B and D. These two ways of dealing with regulatory compliance issues are consistent with Scrum’s values and principles, as they allow the Scrum Team to deliver valuable and potentially releasable increments of the product while meeting the necessary standards and regulations. They also enable the Scrum Team to inspect and adapt their compliance strategy based on feedback and changing requirements.

A is not a good answer because it creates a separate silo of responsibility for compliance issues, which can lead to delays, conflicts, and inefficiencies. It also violates the Scrum value of transparency, as the compliance team may not have full visibility into the product development process.

C is not a good answer because it implies a waterfall approach that assumes all the compliance requirements are known and fixed upfront, which is rarely the case. It also reduces the flexibility and responsiveness of the Scrum Team, as they may have to follow a rigid plan that does not reflect the current reality of the product or the market.

According to the Scrum Guide, two characteristics of the Daily Scrum are its location and time remain constant and its purpose is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog. These characteristics promote consistency, transparency, and adaptation within the Development Team. The other options are not valid characteristics of the Daily Scrum, as they are either irrelevant (such as being held first thing in the morning) or inappropriate (such as being free form, facilitated by the team lead, or consisting of the Scrum Master asking for status).