CSM Service to the Scrum Team Practice Question

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Take the task list from the Product Owner and redistribute it among the Developers based on their skills.

  Why it's wrong here

  The Scrum Master should not take over the planning or assign tasks. This would undermine the Developers' self-management and the Product Owner's role. The Scrum Master's role is to coach and facilitate, not to manage the work. Redistributing tasks may solve the immediate issue but does not address the underlying misunderstanding of Scrum roles and would create dependency on the Scrum Master.

• ✓

  Coach the Product Owner and Developers on the purpose of Sprint Planning, emphasizing that the Developers own the Sprint Backlog and should self-manage how to achieve the Sprint Goal.

  Why this is correct

  Sprint Planning is a collaborative event where the Scrum Team defines the Sprint Goal and the Developers select and plan the work. The Product Owner should not dictate tasks. The Scrum Master serves the team by coaching them on Scrum theory and practices, helping them understand their respective accountabilities. This enables the Developers to self-manage and take ownership of the Sprint Backlog, leading to better commitment and outcomes.

• ✗

  Allow the current practice to continue, since the Product Owner is responsible for maximizing value and knows best what needs to be done.

  Why it's wrong here

  While the Product Owner is responsible for maximizing value, they do not dictate how the work is done. The Developers are accountable for the Sprint Backlog and for self-managing their work. Allowing the Product Owner to assign tasks undermines the team's ability to self-organize and may reduce motivation and creativity. The Scrum Master should intervene to coach the team on Scrum principles.

• ✗

  Suggest that the Product Owner create the Sprint Backlog alone and then hand it to the Developers for execution.

  Why it's wrong here

  The Sprint Backlog is created by the Developers, not the Product Owner. The Product Owner may clarify requirements and priorities, but the Developers own the plan for how to achieve the Sprint Goal. Having the Product Owner create the Sprint Backlog alone reinforces the command-and-control dynamic and prevents the Developers from self-managing, which is contrary to Scrum.