Most Recent Scrum PSM-I Exam Questions & Answers

When many Development Teams are working on a single product, the definition of ''Done'' must be shared by all Development Teams and make their combined work potentially releasable, as stated in [4]: ''When multiple teams work together on one product they must mutually define and comply with the same Definition of Done. This makes sure all Increments adhere to a consistent quality level.''

The correct answers are B, E, and F, because these activities would probably help the team in starting up. Having the Scrum Team members introduce themselves and give a brief background of their skills and work history helps build trust and rapport among them. Ensuring the team understands they need a definition of ''Done'' helps create transparency and alignment on the quality standards for the product. Asking the Product Owner to discuss the product or project, its history, goals, and context, as well as answer questions helps clarify the vision and value of the product.

According to the Scrum Guide, estimates are made by the people doing the work, which is the Development Team. The Development Team is responsible for all estimates in the Product Backlog and the Sprint Backlog. The other options are not valid guidelines for estimating work in Scrum, as they are either too prescriptive (such as requiring story points or relative units), incorrect (such as forbidding estimating or having the Product Owner make estimates), or unnecessary (such as checking estimates with the Development Team).

According to the Scrum Guide1, 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. All events are time-boxed events, such that every event has a maximum duration. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. The time-boxed events in Scrum are:

Sprint Planning (eight hours or less for a one-month Sprint)

Daily Scrum (15 minutes or less for a one-month Sprint)

Sprint Review (four hours or less for a one-month Sprint)

Sprint Retrospective (three hours or less for a one-month Sprint)

The other options are not time-boxed events in Scrum.

According to the Scrum Guide1, there is no such thing as a Release Sprint in Scrum. A Release Sprint implies that there are other Sprints that don't produce a potentially releasable Increment, which violates the core principle of Scrum. Every Sprint should result in a ''Done'', useable, and potentially releasable product Increment.