PSM-I Exam Dumps : Professional Scrum Master I

According to the Scrum Guide 1 , 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.

In Scrum, the term " done " refers to the state where the Increment meets the Definition of Done (DoD), which is a shared understanding within the Scrum Team of what it means for work to be complete. The best two answers are:

C. No work is left to meet the Definition of Done: This statement aligns with the Scrum Guide, which states that the Increment must be in a usable condition and meet the DoD by the end of the Sprint. The DoD ensures that the work is fully completed, tested, and integrated, leaving no outstanding tasks.

D. Ready to be released to end users: This reflects the goal of Scrum that the Increment should be in a potentially releasable state at the end of each Sprint, meaning it is of sufficient quality and functionality to be delivered to users if the Product Owner chooses to do so.

The other options are incorrect because:

A. Ready for integration: While integration is part of the process, " done " implies more than just being ready for integration; it includes being fully completed and meeting the DoD.

B. All work the Developers are willing to do: This is subjective and does not align with the objective standard of the DoD, which is agreed upon by the entire Scrum Team.

E. Whatever the Product Owner defines as quality: The DoD is a team responsibility, not solely defined by the Product Owner, ensuring a collective standard rather than an individual judgment.

According to the Scrum Guide, a Developer becomes accountable for the value of a Product Backlog item selected for the Sprint at the Sprint Planning event. This is when the Developers select items from the Product Backlog that they can commit to complete within a Sprint. The Developers are then responsible for creating a valuable Increment that meets the Definition of Done and the Sprint Goal. The other options are not valid, as they either imply that Developers are not accountable for value (such as never or whenever), or that they become accountable at a different time (such as during the Daily Scrum).