According to the Scrum Guide, a Development Team needs a Sprint Goal because it provides guidance and focus for building an Increment that delivers value. The other options are not valid reasons for having a Sprint Goal, as they are either incorrect (such as giving purpose only to Sprint 0 or ensuring implementation of all Product Backlog items) or irrelevant (such as knowing everything from the Product Backlog).

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.

All of the above topics should be discussed in the Sprint Review, as stated in [4]: 'The purpose of this meeting is to inspect what was delivered during this sprint and adapt what we want to deliver next. This means we will discuss three things:

What did we do this sprint?

How did we do it?

What do we want to do next?'

The correct answer is C, because the Scrum Guide states that ''the Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum. The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box.'' Therefore, the main reason for the Scrum Master to be at the Daily Scrum is to ensure that it happens, but he or she does not have to be there.

The Definition of Done serves the following three purposes:

A . Create a shared understanding of when work is complete.

The Definition of Done is a commitment to the quality of the product increment that is part of Scrum. It is a formal description of the state of the product backlog item or the increment when it meets the quality measures required for the product. The Scrum team must have a shared understanding of what 'done' means and use it to assess when work is complete and transparent1.

C . Increase transparency.

The Definition of Done increases transparency by providing everyone a shared understanding of what work was completed and what standards were met as part of the increment. This ensures that the product increment is potentially releasable and that the stakeholders can inspect and provide feedback on it2.

D . Describe the work that must be mostly done before the Sprint is allowed to end.

The Definition of Done describes the work that must be done before the Sprint is allowed to end. Work cannot be considered part of an increment unless it meets the Definition of Done. The Definition of Done is used to guide the Developers in creating a 'Done', usable, and potentially releasable product increment every Sprint3.

B and E are not purposes of the Definition of Done.

B . Guide the Developers on how many Product Backlog items to select for the Sprint.

The Definition of Done does not guide the Developers on how many Product Backlog items to select for the Sprint. The Developers select how many Product Backlog items they can complete within a Sprint based on their capacity, skills, and experience. The Definition of Done helps them ensure that the selected items are completed to a high standard of quality4.

E . Describe the purpose, Objective, and timebox Of each Scrum event.

The Definition of Done does not describe the purpose, objective, and timebox of each Scrum event. The Scrum Guide describes these aspects for each Scrum event, such as Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective5. The Definition of Done is related to the product increment, not to the Scrum events.