Two techniques that the Scrum Master could use when the Scrum Team gets caught in an internal disagreement about which agile practices to apply are to involve the complete Scrum Team in making a decision, and to use coaching techniques such as open questions and active listening, as stated in [3]: “The Scrum Master should facilitate a constructive dialogue among the team members and help them reach a consensus on which agile practices to use. The Scrum Master should also use coaching techniques such as open questions and active listening to understand the underlying needs and motivations of each team member and to help them find common ground.”

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

An example of an Increment is a valuable, useful set of product features, as stated in [4]: “An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, each Increment must be usable.”

The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The topics that are appropriate for discussion are those that relate to how the team does its work, such as processes, tools, communication, collaboration, quality, etc. The value of work currently represented in the Product Backlog and arranging the Sprint Backlog for the next Sprint are not appropriate topics for discussion in a Sprint Retrospective, as they belong to the Sprint Review and Sprint Planning events respectively.

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.

The correct answer is E, because all of these topics can be discussed during a Sprint Retrospective. The Scrum Guide states that “the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. … During each Sprint Retrospective, the Scrum Team plans ways to improve product quality by adapting the definition of ‘Done’ as appropriate.” Therefore, the Scrum Team can discuss any aspect of their process, communication, skills, or definition of ‘Done’ that may help them improve.

The correct answer is B, because a Product Owner is best described as a value optimizer. The Scrum Guide states that “the Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Therefore, a Product Owner should focus on delivering value to the customers and stakeholders through the product.