I just started as a Scrum Master for a team that has been doing "Scrum-but" for years and is resistant to true Agile principles (e.g., they skip refinement, hate retrospectives). What are the three most critical challenges I should prioritize addressing first, and what practical Scrum techniques can help foster a genuine adoption of Agile mindset and collaboration
3 answers
The three most critical challenges for a new Scrum Master with a resistant team are: 1. Lack of Psychological Safety: The team fears honest feedback, making retrospectives useless. Solution: Start with "Safety Checks" and use non-confrontational formats like the "Mad, Sad, Glad" retrospective to build trust incrementally. 2. Misunderstanding of Self-Organization: The team sees the Scrum Master as a project manager who assigns tasks. Solution: Stop facilitating and start coaching. Ask powerful questions like, "Team, what commitment can you make for this Sprint?" forcing them to take ownership. 3. Skipping Key Events (especially Refinement): This leads to poor Sprint planning and missed Sprint Goals. Solution: Link the skipped event directly to the pain point. Show them how poor refinement led to a stressful mid-sprint scramble, demonstrating the Scrum framework's value as a preventative measure. Focusing on transparency and pain points fosters a true Agile mindset.
That’s spot on about self-organization! I'm curious: when coaching a team that keeps skipping refinement, should the Scrum Master allow a couple of failed Sprints (with no clear Sprint Goal) to demonstrate the pain, or is that too risky and demotivating? Is demonstrating the failure a better teaching tool than just enforcing the Scrum rules?
Prioritize building Psychological Safety (essential for good retrospectives), coaching Self-Organization (shift ownership to the team), and proving the value of Product Backlog Refinement by linking poor refinement directly to poor Sprint outcomes. This is key to successful Scrum Master coaching.
I totally agree, Olivia. If the team doesn't feel safe, the Scrum Master can't truly serve as a servant leader because they won't receive the honest feedback needed to identify systemic impediments. Trust is the foundation of the Scrum framework.
Jason, intentionally allowing failure can be effective, but it must be framed as a controlled experiment. The Scrum Master should first make the team transparently aware of the risk before the Sprint starts (e.g., "Our PBI refinement is weak; I predict this Sprint Goal is at high risk."). If it fails, the retrospective becomes a powerful, undeniable data point. This avoids finger-pointing and reinforces the principle of inspection and adaptation, which is the heart of the Agile mindset. This is far better than simply enforcing a rule they don't understand.