Skip to main content

Facilitation conflict

Last post 07:02 pm December 24, 2023 by Nicholas Gabrichidze
5 replies
05:49 pm December 18, 2023

Hello everyone, 

Have a small question regarding conflict facilitation, usually SM knows how to facilitate things when there is conflict in the team between team members, but how do you guys deal with the toxic attitude from one team member specifically to Scrum Master? I mean it feels like SM is taking this attitude too personally although they barely know each other (due to work remotely) should someone else be involved? Or you think that SM should fix this himself? Or maybe there are some tricks? 

Any ideas will be much appreciated, thanks in advance


10:22 pm December 18, 2023

they barely know each other (due to work remotely)

There's your problem. When was the last time the team got together to collaborate in person and look each other in the eye? How has a foundation for successful remote working been established?


06:34 am December 19, 2023

Yea thats a tricky one since all of them are in different countries and ability to work in one room is very limited


03:59 pm December 20, 2023

Ian's response to your query was accurate. In a team that's still getting to know each other, essential Scrum values such as openness, respect, and courage might be hindered. To address this, the Scrum Master could introduce team-building activities, perhaps dedicating an hour every other Friday to these exercises. Such activities are instrumental in fostering trust and camaraderie among team members. Additionally, the Scrum Master should consider having a candid one-on-one discussion with any individual displaying disrespectful behavior, openly communicating their concerns about the person's attitude. Crucially, the Scrum Master should guide the team in developing a Team Working Agreement. This agreement would outline expected behaviors, emphasizing the importance of treating everyone with equal respect during meetings.


04:06 pm December 20, 2023

Scrum Master focuses building a foundation of trust and acts as a facilitator to resolve issues. Scrum Master learns constantly and improving the way of working together. As a Scrum Master, He or She could apply techniques like asking questions to get to the root cause of the problem and encourages collaborative engagement.


07:02 pm December 24, 2023

Conflicts are natural. The Scrum master role is to make sure that they are turn into productive discussion and not go into personal war. How it should happen depends on mentality, reasons, root cause and coplexity. If you dont know the cause and solution, then treat it as regular complex problem-run a series of small experiments of building relationships around the other side, using various techniques, from one to one to trying to empower other side. It is important to try bringing something another person some value-advice, professional favor else.

More information about various techniques to build relationships https://www.liberatingstructures.com/ls/


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.