Sure Pass Exam PSM-I PDF

According to the Scrum Guide1, collaboration between the Product Owner and Developers is essential for creating valuable products. The Product Owner is accountable for maximizing value resulting from work by Developers. Developers are accountable for creating a plan for the Sprint, which includes selecting items from Product Backlog that they can complete within a Sprint. The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by helping everyone understand Scrum theory and practice, both within the Scrum Team and the organization. Therefore, two valuable actions for a Scrum Master to take if the Product Owner is not collaborating with the Development Team during the Sprint are:

Bring up the problem in the Sprint Retrospective, where the Scrum Team can inspect how they worked together and create a plan for improvements.

Coach the Product Owner in the values of Scrum and incremental delivery, and help them understand their role and responsibilities in collaborating with Developers.

The other options are not valuable actions, as they may undermine trust, respect, and self-organization within the Scrum Team.

References: Scrum Guide

 According to the Scrum Guide1, when multiple Scrum Teams are working together on the same product, they must mutually define and comply with the same definition of “Done”, which includes creating an integrated Increment at least by the end of each Sprint. The Scrum Master should teach and coach the Developers that it is their responsibility to work with other Scrum Teams to create an integrated Increment that meets the definition of “Done”. The other options are not aligned with Scrum values and principles.

References: Scrum Guide

Architecture and infrastructure are handled in Scrum by implementing them along with functional development of the product, and by adding them to the Product Backlog and addressing them in early Sprints, while always requiring at least some business functionality, no matter how small, as stated in [2]: “Scrum does not distinguish between developing functionality or architecture. They are developed together, as they are both important and support each other. Architecture is not a separate phase; it is part of the product development. Architecture is added to the Product Backlog as any other feature or functionality.”

According to the Scrum Guide, every Scrum Team should have the competencies and skills needed to deliver an Increment in a Sprint. This means that the Developers can work on any aspect of the product without depending on others outside the team. The other options are not valid descriptions of what every Scrum Team should have, as they either imply that the Developers work in silos or rely on external people (such as a lead developer or representatives from different departments).