Facilitatingis the activity that seeks to build consensus in a group setting. In Scrum, the Scrum Master often acts as afacilitator, helping the team reach agreements during events such as Sprint Planning, Retrospectives, or backlog refinement sessions. Facilitators guide discussions neutrally, ensuring all voices are heard and helping the group align on decisions.
According to the2020 Scrum Guide, the Scrum Master:
* Facilitates Scrum events as requested or needed.
* Removes barriers to communication and fosters collaboration within the team.
Why the other options are incorrect:
* A. Coaching:Coaching involves guiding individuals or teams to improve performance, but it is not specifically about building group consensus.
* B. Teaching:Teaching focuses on imparting knowledge, not consensus-building.
* C. Mentoring:Mentoring involves a one-on-one relationship where the mentor shares knowledge and experience, which is not a group activity.

TheSprint Retrospectiveis heldafter the Sprint Review and before the next Sprint Planning. It is the final event in the Sprint, and its purpose is to reflect on the past Sprint and identify areas for improvement. The Scrum Team inspects how they worked during the Sprint in terms of processes, interactions, tools, and the Definition of Done, and then adapts for future Sprints.
According to the2020 Scrum Guide:
* The Sprint Retrospective is time-boxed and enables the team to inspect and adapt their working practices.
* It helps improve the Scrum Team's effectiveness in subsequent Sprints.
Why the other options are incorrect:
* B. At the beginning of the Sprint:The Sprint Retrospective is not held at the start of the Sprint. Sprint Planning occurs at the beginning of the Sprint.
* C. In the middle of the Sprint:Mid-Sprint is not a designated time for this meeting; the team is focused on achieving the Sprint Goal.
* D. At the end of all the Sprints:The Retrospective is held at the end ofeach Sprint, not at the conclusion of all Sprints.

Scrum teams plan workone Sprint at a time, using theSprint Planning eventto adapt the Sprint Backlog based on what was learned in previous Sprints. This approach aligns with Scrum'sempirical process control, which relies on inspection and adaptation to plan effectively.
According to the2020 Scrum Guide:
* Sprint Planning creates aSprint Backlog, which includes the Sprint Goal, selected Product Backlog items, and the plan to deliver them.
* Teams adjust their plans Sprint by Sprint, responding to new information, feedback, and changing circumstances.
Why the other options are incorrect:
* A. One release at a time, adjusting the number of Sprints to the prior releases' average velocity:
Scrum does not prescribe release-driven planning or adjusting Sprint duration based on velocity.
* C. One project at a time, adjusting each Sprint Backlog Item to meet the release date negotiated at inception:Scrum encourages iterative planning within Sprints, not fixed plans tied to predetermined release dates.
* D. One Sprint at a time in the Product Backlog Refinement meeting with participation of stakeholders:Product Backlog Refinement is an ongoing activity, not a Sprint planning process.
Stakeholders typically participate in Sprint Reviews, not in backlog refinement.

Thetypical size of an effective Scrum Team is ten or fewer people, as stated in the2020 Scrum Guide. This includes the Product Owner, Scrum Master, and Developers. Smaller teams ensure better communication, collaboration, and effectiveness, as larger teams can introduce inefficiencies and coordination challenges.
Why the other options are incorrect:
* B. Size doesn't matter as long as the Scrum Master coordinates the work in collaboration with the Product Owner:Scrum Teams are self-managing and self-organizing; they do not rely on the Scrum Master to coordinate work. Team size does matter for effectiveness.
* C. Bigger teams communicate better, are more productive and produce better results:Larger teams often face communication and coordination challenges, reducing productivity and effectiveness.
* D. When a team expands beyond ten, activities, like verification and operations, are assigned to a different team:Scrum encourages cross-functional teams that handle all activities required to deliver a usable Increment without assigning work to other teams.

The Product Owner is accountable forcreating and ordering Product Backlog itemsto maximize the value of the product. This includes clearly expressing Product Backlog items, ordering them to maximize value, and ensuring that the Product Backlog is transparent and understood.
According to the2020 Scrum Guide, the Product Owner is accountable for:
* Maximizing the value of the product resulting from the work of the Scrum Team.
* Effectively managing the Product Backlog by ensuring it is prioritized and transparent.
* Creating Product Backlog items in collaboration with stakeholders and the Scrum Team.
Why the other options are incorrect:
* A. Describe the solution:The Product Owner defines the "what" (desired outcomes), not the technical
"solution," which is determined by the Developers.
* B. Manage the Developers:The Product Owner does not manage the Developers. Developers are self- managing and self-organizing.
* D. Recognize titles:Titles have no significance in Scrum, and this is not a responsibility of any Scrum role.