Study guide
6.5 Conflict & Organizational Change
PSM I — Professional Scrum Master I Scrum.org
Track your progress as you read
Finished sections get a check mark.
1 Introduction & PSM I Exam Overview
1.1 Current PSM I Exam Facts 1.2 Scoring & Time-Management Strategy 1.3 The 2020 Scrum Guide Is The Single Source Of Truth 1.4 A Realistic PSM I Study Plan
2 Scrum Theory, Empiricism & Values
2.1 What Scrum Is (and Is Not) 2.2 Empiricism and Empirical Process Control 2.3 The Three Pillars: Transparency, Inspection, Adaptation 2.4 Lean Thinking: Reduce Waste, Focus on Essentials 2.5 The Five Scrum Values
3 The Scrum Team & Accountabilities
3.1 The Scrum Team 3.2 The Developers 3.3 The Product Owner 3.4 The Scrum Master 3.5 Scrum Master Services to Team, Product Owner, and Organization
4 The Scrum Events
4.1 The Sprint 4.2 Sprint Planning 4.3 The Daily Scrum 4.4 The Sprint Review 4.5 The Sprint Retrospective 4.6 Timeboxing and Empiricism Across the Events
5 Scrum Artifacts & Commitments
5.1 Artifacts & the Transparency Mandate 5.2 Product Backlog & the Product Goal 5.3 Sprint Backlog & the Sprint Goal 5.4 The Increment & the Definition of Done 5.5 Commitments Summary & Exam Traps
6 Developing People & Teams
6.1 Self-Managing Teams 6.2 Facilitation 6.3 Scrum Master Stances 6.4 True Leadership That Serves 6.5 Conflict & Organizational Change
7 Managing Products with Agility
7.1 Product and Value 7.2 Product Goal Management 7.3 Product Backlog Management 7.4 Forecasting and Release Planning 7.5 Stakeholders, Evidence, and Business Agility
8 Final Review & Exam Strategy
8.1 Common Misconceptions & PSM I Traps 8.2 2020 Scrum Guide Rapid Review 8.3 Question Tactics & Time Management 8.4 Last-Minute Checklist
6.5 Conflict & Organizational Change
Key Takeaways Explain This Topic AI
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.
Last updated: June 2026
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.