What action should a Scrum Master take if the Development Team has decided that Retrospectives are no longer necessary?

Question

Options

• AStart facilitating more productive and useful Retrospectives.
• BSuggest reducing the frequency of the Retrospectives.
• CExtend the Sprint time-box in order to fit the Retrospectives.
• DComply with the team's decision.

• A
  84% (31)
• B
  5% (2)
• C
  8% (3)
• D
  3% (1)

Explanation

Retrospectives are a mandatory Scrum event, and the Scrum Master is accountable for ensuring Scrum is understood and enacted - so when a team wants to abandon them, the right move is to improve their quality, not eliminate or reduce them. A is correct because the Scrum Master's responsibility is to make Retrospectives valuable enough that the team wants them, not to simply comply with a decision that violates the Scrum framework. B is wrong because reducing frequency still violates the Scrum Guide, which requires a Retrospective after every Sprint. C is wrong because Sprint length is not changed to accommodate events - all Scrum events must fit within the fixed Sprint time-box. D is wrong because the Scrum Master serves the team partly by protecting the integrity of Scrum, even against the team's own preferences.

Memory tip: Think of the Scrum Master as a "process guardian" - their job is never to remove Scrum events, but to make them work better. If something isn't working, fix it, don't skip it.

No community discussion yet for this question.