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.

• ✓

  Coach senior leadership on the true purpose of the Sprint Review as a collaborative inspection event focused on the increment and adaptation.

  Why this is correct

  Educating stakeholders ensures they understand that the Sprint Review is an inspect-and-adapt session, not a high-stakes interrogation or individual performance review. This systemic coaching prevents future boundary violations and realigns leadership expectations with agile inspection principles.

• ✗

  Prohibit senior leadership from attending future Sprint Reviews to shield the team from uncomfortable questioning.

  Why it's wrong here

  Excluding stakeholders breaks transparency and prevents the team from receiving crucial market and user feedback required for empirical adaptation. The Scrum Master must coach stakeholders rather than locking them out of vital collaborative feedback loops.

• ✓

  Work with the Product Owner to ensure stakeholders are actively engaged in meaningful discussions around product increment progress and backlog adaptation.

  Why this is correct

  Redirecting leadership toward substantive dialogue about the increment and backlog adaptation replaces micromanagement with genuine stakeholder collaboration. This preserves the Sprint Review's purpose, restores the team's autonomy and self-management, and addresses the morale and velocity decline caused by excessive oversight.

• ✗

  Cancel all future Sprint Reviews and replace them with private status presentations delivered by the Scrum Master directly to the executives.

  Why it's wrong here

  Cancelling Sprint Reviews removes the inspect-and-adapt event that surfaces the team's work, and private executive briefings hide information from the Scrum Team, worsening the micromanagement problem. It is tempting as a way to shield the team from leadership pressure, but the Scrum Master should instead coach leadership on Review purpose and facilitate transparent collaboration.

• ✗

  Advise the developers to ignore stakeholder feedback entirely if they disagree with the tone or direction of the executive commentary.

  Why it's wrong here

  Advising the team to ignore feedback dismisses the core empirical intent of gathering market intelligence from stakeholders. The team must learn to separate constructive product feedback from unhelpful delivery pressure without shutting out stakeholder perspectives.