Coaching Agile Teams Through Conflict: Levels, Moves, Escalation

Every team that works closely together will disagree. Agile teams may disagree more visibly than most, because they plan, estimate and review work together and inspect their own process every few weeks. That visibility is healthy: problems come into the open where they can be dealt with.

The challenge for an agile coach or Scrum Master is telling the difference between disagreement that moves the team forward and conflict that is starting to damage it, then responding in proportion. Overreact and you teach the team that disagreement is dangerous. Underreact and a fixable problem hardens into factions.

This guide covers one well-known way of reading how serious a conflict is, practical facilitation moves for each stage, and the situations where a coach should stop facilitating and escalate.

Conflict Is Not the Enemy

Lyssa Adkins's 2010 book Coaching Agile Teams devotes a chapter to the coach as "conflict navigator." In the book's summary of that chapter, she describes the coach's job as helping the team "navigate through conflict and into the desired state of constructive disagreement." The aim is not a team that never argues. It is a team that argues about the work, in the open, and comes out with better decisions.

The Scrum Guide points the same way. Its five values include openness, respect and courage, and it says team members "have the courage to do the right thing, to work on tough problems." A team that avoids every hard conversation is not living those values, however calm it looks.

Reading the Level of Conflict

In the same chapter, Adkins presents five levels of conflict that form an escalation path. At the bottom is ordinary problem-solving, where people differ but are focused on the problem. Above it are levels she calls disagreement, contest, crusade and, at the top, world war. The names themselves suggest how the stakes rise as a conflict escalates.

You do not need to memorize a taxonomy to use the idea. The practical point is that the right response depends on the level, so a coach should diagnose before intervening. Adkins points to the language people use as one useful clue. Some general signals to listen for, offered here as practical guidance rather than a formal scale:

• Lower levels: people talk about the work ("the API design," "the test approach"), share information freely and can describe the other person's view fairly.
• Middle levels: conversation shifts to people and positions ("they always," "she never"), information is held back, and side conversations start replacing team discussion.
• Higher levels: people talk about sides, recruit allies, question each other's motives or competence, or describe the goal as making the other party lose.

If you are unsure, ask. A quiet one-on-one question often reveals more than observation.

Facilitation Moves at Lower Levels

When conflict is still about the work, the coach's role is mostly to protect the conversation, not to solve the problem.

1. Name it neutrally. "It sounds like we have two different views on how to split this story. Let's look at both." Naming a disagreement out loud makes it a legitimate topic rather than an undercurrent.
2. Separate interests from positions. The Harvard Negotiation Project's book Getting to Yes, by Roger Fisher, William Ury and Bruce Patton, recommends focusing on interests, not positions, and inventing options for mutual gain. In team terms, ask each side what they are trying to protect, such as speed, quality or maintainability, before debating solutions.
3. Make the criteria explicit. Agree on how the team will judge options (for example, risk, cost of delay or the Definition of Done) before choosing one.
4. Timebox and decide. Long, unstructured debate tends to escalate. Give the discussion a timebox, then use a decision method the team already trusts. Our guide to facilitation techniques for agile teams covers options such as fist of five.
5. Run small experiments. Many technical disagreements can be settled by trying one approach for a Sprint and inspecting the results at the retrospective.

Facilitation Moves at Middle Levels

Once people start protecting themselves or trying to win, group discussion alone is often not enough.

• Talk with each person privately first. Listen without agreeing or disagreeing, and help them separate what happened from their interpretation of it.
• Bring people together only with ground rules. Agree that each person states the other's view to the other's satisfaction before arguing their own.
• Revisit working agreements. If the team has none, creating them together can turn a personal clash into a team decision about how everyone will work.
• Look for structural causes. Unclear accountabilities, competing goals from different managers or impossible deadlines often sit behind what looks like a personality clash. The Scrum Guide describes the Scrum Master as "causing the removal of impediments," and a structural cause of conflict is an impediment.
• Reflect on conflict styles. The Thomas-Kilmann Conflict Mode Instrument describes five conflict-handling modes: competing, accommodating, avoiding, collaborating and compromising. Its publisher states that no single mode is best and that the right choice depends on the situation. Discussing these modes can help a team see that a colleague who "always gives in" or "always pushes" is using a habitual mode, not acting in bad faith.

When to Escalate

A coach facilitates; a coach is not HR, legal counsel or security. Escalate, usually to the relevant manager or HR, when any of the following apply:

• Harassment or discrimination. The US Equal Employment Opportunity Commission encourages employees to report harassment to management at an early stage to prevent its escalation. Conduct of this kind is not a team-dynamics issue to mediate in a retrospective.
• Threats, intimidation or any concern about physical safety. Involve the organization's security or emergency procedures, and call 911 in an emergency.
• Conflict at the highest levels, where people are trying to harm each other's reputation or careers. At that point, team facilitation can make things worse, and the people involved may need a trained mediator or management action.
• A conflict that stems from decisions above the team, such as two executives giving contradictory priorities. The team cannot resolve that alone.
• Signs that someone is in distress. Coaching is not a substitute for professional care. Encourage the person to seek appropriate support, such as an employee assistance program if one exists, and in a crisis in the US, call or text 988.

When you escalate, tell the people involved what you are doing and why, unless that would put someone at risk. Transparent escalation protects trust.

A Hypothetical Example

Imagine two senior developers on an eight-person team who disagree about whether to rewrite a fragile module. At first, the debate is about risk and timelines. Over a few Sprints, it turns into sarcastic comments in code reviews, and other team members start choosing sides.

The coach meets each developer separately, listens, and learns that both are worried about the same thing: being blamed if the release slips. The coach then facilitates a session where the team lists the interests at stake, agrees on criteria, and decides to try a time-boxed spike to gather data. The coach also raises the blame concern with the engineering manager, because fear of blame is a system issue, not a personal one. This example is illustrative, not a promise of how any real team would respond.

Key takeaways

• The goal is constructive disagreement, not the absence of conflict.
• Lyssa Adkins describes five escalating levels of conflict; diagnose the level before choosing a response.
• At lower levels, protect the conversation by naming the issue, separating interests from positions and timeboxing decisions.
• At middle levels, work one-on-one first, set ground rules and look for structural causes.
• Escalate harassment, threats, safety concerns and conflicts rooted in decisions above the team rather than facilitating them yourself.

Sources

• Lyssa Adkins, Coaching Agile Teams (Addison-Wesley, 2010), publisher page with table of contents
• Lyssa Adkins, Coaching Agile Teams, sample pages including chapter overview and index (PDF)
• Ken Schwaber and Jeff Sutherland, The 2020 Scrum Guide
• Harvard Law School Program on Negotiation, Harvard Negotiation Project
• The Myers-Briggs Company, Thomas-Kilmann Conflict Mode Instrument (TKI)
• US Equal Employment Opportunity Commission, Harassment
• 988 Suicide and Crisis Lifeline