New Release PSM-I Professional Scrum Master Questions

According to the Scrum Guide, a Development Team is cross-functional if it has all the skills to create a potentially releasable Increment by the end of every Sprint. The other options are not indicators of cross-functionality, as they are either specific practices (such as pair programming or test driven development) or irrelevant factors (such as conflicts within the team or ability to perform every task).

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

he correct answer is A, because doing all work needed to meet the definition of “Done” enhances the transparency of an increment. The Scrum Guide states that “when a Product Backlog item or an Increment is described as ‘Done’, everyone must understand what ‘Done’ means.” Therefore, by meeting the definition of “Done”, an increment becomes transparent to all stakeholders and ready for release.

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.

References: Scrum Guide