6.5 Conflict & Organizational Change
Key Takeaways
- Team development moves through stages (Tuckman's forming, storming, norming, performing); the 'storming' stage is normal conflict the Scrum Master should expect and facilitate, not suppress.
- Healthy task/process conflict can improve outcomes; the Scrum Master facilitates productive disagreement and de-escalates destructive interpersonal conflict, letting the team resolve it where possible.
- The Scrum Guide makes the Scrum Master accountable for helping remove impediments; impediments the team cannot clear are escalated to the organization, not absorbed silently.
- The Scrum Master serves the larger organization as a change agent — causing the removal of barriers between stakeholders and the Scrum Team and leading Scrum adoption beyond a single team.
- Organizational change is influence, not authority: the Scrum Master uses transparency, data, coaching of leaders, and incremental adoption — not mandates — to spread agility.
Why Conflict and Change Belong Together
The "Developing People and Teams" competency includes the friction a Scrum Master must navigate: conflict inside the team and impediments/change in the organization around it. The 2020 Scrum Guide makes the Scrum Master accountable for the Scrum Team's effectiveness and for serving the organization by causing the removal of barriers between stakeholders and Scrum Teams. How that is done well is professional facilitation and change practice — the techniques are Scrum.org competency content, not Scrum Guide rules.
Team Development Stages (Tuckman)
A widely cited model of team development is Bruce Tuckman's sequence: forming → storming → norming → performing (with an optional adjourning when the team disbands). It is professional practice, not a Scrum rule, but it explains why new teams struggle and why conflict is normal:
| Stage | What Happens | Scrum Master Focus |
|---|---|---|
| Forming | Polite, uncertain; members orient | Teach Scrum, set working agreements, clarify accountabilities |
| Storming | Disagreement, friction over roles and approach | Normalize conflict, facilitate it productively, protect safety |
| Norming | Shared norms and trust emerge | Coach lighter; reinforce self-management |
| Performing | High-trust, effective self-management | Mostly light coaching plus change-agent work |
The key insight for PSM I: storming is expected, not a failure. A Scrum Master who tries to eliminate all conflict actually stalls a team in forming. The goal is to move conflict from destructive to productive, not to remove it.
Healthy vs Destructive Conflict
- Healthy conflict is about ideas, design, or process — it surfaces options and improves decisions. The Scrum Master facilitates it, keeps it respectful, and protects the team's right to decide.
- Destructive conflict is personal, status-driven, or fear-driven — it shuts people down. The Scrum Master de-escalates, restores psychological safety, and addresses behavior, often outside the event itself.
| Aspect | Healthy (Encourage) | Destructive (De-escalate) |
|---|---|---|
| Focus | Ideas, design, process | People, status, blame |
| Effect | Better decisions, more options | Silence, withdrawal, fear |
| SM action | Facilitate, keep it safe | Restore safety, address behavior |
| Decision owner | The team | The team, once safety is restored |
Facilitating Conflict Without Taking Sides
The Scrum Master owns the process of resolving disagreement and stays neutral on the content. For a technical disagreement between Developers, the Scrum Master does not pick the architecture; the Scrum Master helps the Developers agree on how they will decide — a spike, a time-boxed experiment, Definition-of-Done criteria, or a clear decision rule — and lets them own the outcome. Choosing the decision for a self-managing team breaks a Scrum Guide rule, even when it is faster.
Impediments and Escalation
An impediment is anything slowing the team that they cannot reasonably clear themselves. The Scrum Master:
- Helps the team resolve what is within its control (coaching them to self-manage it).
- Removes or escalates what is not — to the right person or part of the organization.
- Makes impediments transparent rather than quietly absorbing them.
Silently absorbing organizational impediments is a classic anti-pattern: it hides systemic problems, lets them recur, and prevents the organization from improving. Transparency is the lever that turns a hidden blocker into an organizational decision.
The Scrum Master as Change Agent
Scrum adoption beyond one team is influence work, not authority. The Scrum Master serves the larger organization, but holds no command power over it. Effective change behaviors:
- Coach leaders and stakeholders on what Scrum needs: self-management, empiricism, a single empowered Product Owner, and a real Definition of Done.
- Make problems transparent with data and outcomes (cycle time, escaped defects, value delivered) rather than opinions.
- Adopt incrementally — treat the change itself empirically: inspect and adapt it Sprint by Sprint.
- Cause the removal of barriers between stakeholders and teams instead of routing everything through the team or becoming a bottleneck.
- Never mandate culture; model it, create the conditions for it, and let it grow.
A PSM I distinction worth memorizing: leading organizational change is a Scrum Master service, but the specific change-management techniques are professional practice, not Scrum Guide rules — do not over-claim them as framework requirements. The exam rewards answers that influence and make transparent over answers that command or quietly absorb.
Conflict-Resolution Modes and a Quick Decision Guide
A classic lens (Thomas-Kilmann) describes five conflict modes — competing, accommodating, avoiding, compromising, and collaborating. The Scrum Master generally steers a team toward collaborating (work the problem together for the best joint outcome) for important task conflicts, while using lighter modes for trivial ones. It is professional practice, not a Scrum rule, but it frames why 'collaborate to a better decision' usually beats 'compromise quickly' or 'avoid the issue.'
A quick decision guide for exam scenarios:
- Is the conflict about ideas/design/process? Facilitate it; keep it safe; the team decides.
- Is it personal or fear-driven? De-escalate, restore safety, address behavior — often privately.
- Can the team resolve the blocker itself? Coach them to self-manage it.
- Is the blocker organizational? Make it transparent and escalate; never absorb it silently.
- Does spreading Scrum require a culture shift? Influence, coach leaders, show data, and adopt incrementally — never mandate.
The through-line for this entire competency: the Scrum Master grows people and teams by serving, facilitating, coaching, and making problems transparent — protecting self-management and empiricism rather than taking control.
Two Developers strongly disagree on a system design, slowing the Sprint. Neither will concede. What is the BEST Scrum Master action, consistent with self-management and a facilitation stance?
A team in its first few Sprints is experiencing open disagreement about roles and working approach. How should the Scrum Master interpret and respond to this 'storming'?
The team is repeatedly blocked by a slow centralized environment-provisioning team it does not control. The Scrum Master has informally worked around it for months. What should change?
Order the steps the Scrum Master should follow when an impediment outside the team's control surfaces.
Arrange the items in the correct order