Conflict Resolution Dynamics – PSM II Guide
Conflict Resolution and Team Dynamics in Scrum
Understanding conflict resolution and team dynamics is a critical competency for any Scrum Master, especially at the PSM II level. This guide covers why it matters, what it entails, how it works in practice, and how to confidently answer exam questions on the topic.
Why Is Conflict Resolution Important in Scrum?
Scrum Teams are self-managing, cross-functional groups of people who collaborate intensively. Wherever there is collaboration, there is the potential for conflict. Conflict is not inherently negative—in fact, healthy conflict can lead to better decisions, deeper understanding, and stronger team cohesion. However, unresolved or destructive conflict can erode trust, reduce productivity, and damage morale.
A Scrum Master operating at the PSM II level is expected to:
- Recognize that conflict is natural and sometimes beneficial
- Understand how to foster healthy disagreement while preventing destructive patterns
- Coach the team to resolve their own conflicts rather than always intervening directly
- Create an environment of psychological safety where people feel comfortable raising concerns
What Is Conflict Resolution in a Scrum Context?
Conflict resolution in Scrum refers to the approaches, techniques, and mindsets used to address disagreements, tensions, and competing interests within or around a Scrum Team. It encompasses:
1. Sources of Conflict:
- Differing technical opinions on how to implement a solution
- Unclear Product Backlog items leading to misunderstandings
- Role ambiguity or overstepping accountability boundaries
- Personality clashes and communication style differences
- Organizational impediments creating pressure on the team
- Competing priorities between stakeholders and the team
2. Types of Conflict:
- Task conflict: Disagreements about the work itself (often healthy)
- Process conflict: Disagreements about how work should be done
- Relationship conflict: Personal friction between individuals (often destructive)
3. Levels of Conflict:
Understanding the intensity of conflict helps the Scrum Master choose the right approach. A widely referenced model is Lyssa Adkins' five levels of conflict (adapted from Speed Leas):
- Level 1 – Problem to Solve: Differences exist but people collaborate openly. Information sharing and dialogue resolve the issue. This is the ideal level.
- Level 2 – Disagreement: People begin to protect themselves. They may withhold information or use guarded language. The Scrum Master should facilitate open discussion and active listening.
- Level 3 – Contest: The goal shifts from solving the problem to winning the argument. Factions may form. The Scrum Master needs to mediate and refocus the team on shared goals.
- Level 4 – Crusade: People believe the other party must be removed or fundamentally changed. Ideology replaces pragmatism. External facilitation or management intervention may be needed.
- Level 5 – World War: The goal is destruction of the other party. This is rare in professional settings but requires immediate organizational intervention.
How Does Conflict Resolution Work in Practice?
The Scrum Master's Role:
The Scrum Master serves the team as a facilitator, coach, and servant-leader. In the context of conflict, this means:
- At Level 1-2: The Scrum Master encourages the team to resolve conflicts themselves. They might use facilitation techniques during Sprint Retrospectives, create working agreements, or coach individuals on communication skills. The emphasis is on teaching the team to fish, not resolving every issue directly.
- At Level 3: The Scrum Master may need to step in more actively as a mediator. Techniques include:
• Bringing parties together in a neutral setting
• Using active listening and restating each person's perspective
• Refocusing on shared objectives and the Sprint Goal
• Asking powerful coaching questions rather than providing solutions
- At Level 4-5: The Scrum Master may need to escalate and involve management or HR. These levels are beyond what a Scrum Master alone can typically resolve.
Key Techniques and Approaches:
1. Thomas-Kilmann Conflict Modes: Understanding five approaches to conflict—Competing, Accommodating, Avoiding, Compromising, and Collaborating. In Scrum, collaborating is generally the preferred mode because it seeks a win-win solution. However, the appropriate mode depends on context:
- Collaborating: Best when both parties' concerns are important and time allows for deep discussion
- Compromising: Useful when a quick, mutually acceptable solution is needed but neither party gets everything
- Accommodating: Appropriate when the issue matters more to the other party and preserving the relationship is key
- Competing: Rare in Scrum but may be needed in emergencies where a quick decision is critical
- Avoiding: Temporarily appropriate when emotions are too high, but should not be a long-term strategy
2. Facilitated Retrospectives: The Sprint Retrospective is the Scrum event most directly tied to team dynamics. A skilled Scrum Master uses varied retrospective formats to surface hidden tensions, celebrate successes, and create actionable improvements. Techniques include safety checks, anonymous input, structured turn-taking, and focused exercises like the Sailboat or Starfish retrospective.
3. Working Agreements: Teams that co-create explicit norms about communication, decision-making, and behavior are better equipped to handle conflict. Examples: "We address disagreements openly in the team rather than through side conversations" or "We assume positive intent when interpreting a teammate's actions."
4. Coaching Stance: Rather than telling people what to do, the Scrum Master asks open-ended, powerful questions:
- "What outcome would be best for the team?"
- "What assumptions might you be making about the other person's intent?"
- "How does this conflict relate to our Sprint Goal?"
5. Creating Psychological Safety: Research by Google (Project Aristotle) found that psychological safety is the number one factor in high-performing teams. The Scrum Master fosters this by modeling vulnerability, celebrating learning from mistakes, and protecting team members from blame culture.
Team Dynamics Models:
Understanding team development helps the Scrum Master anticipate and normalize conflict:
- Tuckman's Stages: Forming → Storming → Norming → Performing (→ Adjourning). Conflict is most prominent in the Storming phase, where team members test boundaries and challenge each other. This is a necessary phase. The Scrum Master should not try to skip it but should guide the team through it constructively.
- A Scrum Master who understands Tuckman's model will not panic when conflict arises in a newly formed team. Instead, they recognize it as a sign of growth and help the team establish norms that move them toward the Performing stage.
Common Scenarios in PSM II Exam Context:
Scenario 1: Two developers disagree on architectural approach.
Best response: Encourage them to discuss their options openly with the team, evaluate trade-offs against the Sprint Goal and Definition of Done, and let the Developers make the technical decision. The Scrum Master does NOT make the technical decision.
Scenario 2: A team member consistently dominates discussions and others withdraw.
Best response: The Scrum Master addresses the dynamic, possibly privately coaching the dominant individual and using facilitation techniques (e.g., round-robin, silent brainstorming) to ensure all voices are heard. The Retrospective is also a good venue to surface this.
Scenario 3: The Product Owner and Developers are in a heated disagreement about Sprint scope.
Best response: The Scrum Master facilitates a conversation focused on the Sprint Goal and helps both parties understand each other's constraints. The Product Owner has final say on what to build; the Developers have final say on how much they can take on.
Scenario 4: A conflict has escalated to personal attacks between two team members.
Best response: The Scrum Master intervenes, possibly speaking with individuals privately first, then facilitating a joint discussion if appropriate. If the conflict is at Level 4 or 5, management involvement may be necessary.
Exam Tips: Answering Questions on Conflict Resolution and Team Dynamics
1. Remember the Scrum Master is a facilitator, not a dictator. The best answers almost always involve coaching, facilitating, and empowering the team—not commanding, directing, or making decisions for others. If an answer choice has the Scrum Master telling the team what to do, it is likely wrong.
2. Conflict is not always bad. If a question implies that all conflict should be eliminated, that is a trap. Healthy disagreement leads to better outcomes. The goal is to keep conflict at a constructive level (Level 1-2), not to eliminate it entirely.
3. Self-management is paramount. The Scrum Guide emphasizes that Scrum Teams are self-managing. Answers that encourage the team to resolve their own conflicts (with facilitation support) are generally preferred over answers where the Scrum Master solves the problem unilaterally.
4. Look for the coaching approach. PSM II is testing for advanced Scrum Mastery. Answers that involve asking powerful questions, helping people see different perspectives, and fostering understanding are typically correct over answers that involve escalation or avoidance.
5. Context matters—match the intervention to the conflict level. A Level 1 conflict does not need mediation. A Level 4 conflict cannot be solved by simply asking a coaching question. Choose the response proportional to the severity.
6. Understand Tuckman's model. If a question describes a new team experiencing friction, recognize this as the Storming phase. The correct answer will involve helping the team through it, not disbanding the team or avoiding the conflict.
7. Collaboration over compromise. When given a choice between collaborating (win-win) and compromising (each side gives something up), collaboration is usually the preferred answer in Scrum, though compromise can be acceptable in time-sensitive situations.
8. The Retrospective is the primary inspect-and-adapt event for team dynamics. Many correct answers will reference the Sprint Retrospective as the appropriate venue to address interpersonal and process-related conflicts.
9. Beware of answers that involve removing people from the team. This is rarely the correct first response. Coaching, facilitation, and creating transparency are preferred. Removal is a last resort (Level 4-5 conflict).
10. Psychological safety is foundational. If a question asks what the Scrum Master should prioritize for team health, creating an environment where people feel safe to speak up, disagree, and admit mistakes is almost always the right foundation.
11. Don't confuse the Scrum Master's role with a manager's role. The Scrum Master does not conduct performance reviews, assign work, or discipline team members. Their influence comes through facilitation, coaching, mentoring, and teaching.
12. Read all answer options carefully. PSM II questions often have multiple plausible answers. Look for the one that best reflects Scrum values (Commitment, Focus, Openness, Respect, Courage), empiricism, and servant-leadership.
Summary
Conflict resolution and team dynamics are at the heart of effective Scrum Mastery. A PSM II-level Scrum Master understands that conflict is natural, knows how to assess its severity, chooses appropriate interventions, and—above all—empowers the team to develop their own conflict resolution capabilities. By mastering these concepts and applying the exam tips above, you will be well-prepared to handle both the exam questions and real-world Scrum challenges with confidence.
