Skip to main content

My first job as Scrum Master (and my first difficult situation)

Last post 01:29 pm March 23, 2018 by Jeremy Saal
8 replies
12:02 pm March 21, 2018

Hi everyone,

I am new here and a "beginner" regarding the Scrum Master role. I really like this community!

Some months ago, I started as a Scrum Master in a small team and still love this role! But now I am in a situation, which is really difficult for me.

There is a complaint about one of my developers regarding his way of working and his behavior/communication to colleagues outside the team. The complaint was adressed to me (via mail) and not to him directly. He doesn't show a similar behavior inside the team.

I am not sure what to do here:

  1. Talk to this developer in person (one-to-one) about the complaint (is this way too "direct"/"top down" in my role of a Scrum Master?)
  2. Bring this topic to the Retrospective (in the context of a general topic, e.g. "How do we communicate inside and outside the team?") - Here is my concern, that it won't solve this specific conflict.
  3. Talk to the whole team about the complaint (when is the best time for that?)
  4. Or completely different?

Have you ever had a similiar situation? Or do you have any further advices for me?

Thank you very much in advance!

Marc


06:55 pm March 21, 2018

Nice question, and congratz on working in what you love bro :)

 

As we know, communication is essencial for the sucess of the SCRUM framework. Surely, communication problems can be solved in retrospective, but why wait for it? The principle of adaptation has to happen all the time with the ongoing devolepment of the team. 

You can talk to this developer one-to-one, but not in a top down way, but in a team collegue way. Or you can let the team work itself naturally,  in my opinion it will eventually happen if you give the right authority to people. 

That's my opinion, I hope it will help you!!! 

Good luck bro!

From SM to SM!


08:41 pm March 21, 2018

I'd suggest working with whoever raised the complaint directly, and find out more about what's going on. At the moment, there doesn't appear to be any evidence that the substance is:

- factually correct

- fair

- an impediment to collaboration

It might be all of those things, in which case it needs to be taken to the team. However until you have more information, for all you know at this stage, you could have a team member who is being unjustly accused and who needs defending.


06:22 am March 22, 2018

Thank you Thiago and Ian! This helps a lot - it’s always great to get some input from other Scrum Masters! I‘ll go the next step here ... I am pretty sure that this is a perfect situation to learn and improve!


09:50 am March 22, 2018

Hello Marc,

I appreciate your concern for your team member. However, it is a behavioral/communication issue exhibited by him outside the project and I assume here that complaint is not from client. As Scrum Master you are not responsible for this. Every employee is bound by company HR policies and he has to abide by them. As a mentor you can have discussion with him over coffee and get more details. If HR gets into this, it may impact your team.


10:46 am March 22, 2018

Thank you Ian, I have not thought about this aspect :/


04:19 pm March 22, 2018

In fact, there's a kind of unwritten rule to praise in front of an audience and to reprimand one-to-one.

IMHO, your reaction should depend on how serious complaint was. If it was about breaking any fundamental interpersonal rules you should act immediately. If it wasn't that serious working on with both sides of the conflict might be beneficial. 


09:08 am March 23, 2018

First don't panic.

Second, identify root of the issue. Is happening regularly, under what circumstances?

Who has sent you an email, person who has been abused or this issue emerged to a high level management? (If not, try to minimize people involved, and do not disseminate information about the incident, until you know all the details)

Try to gather as much information as possible about the incident, from all involved parties. 

Base on this information you can decide what to do next

Next steps probably are :

(Conduct analyze, possible solutions, risk/impact and aftermath of each solution).

If you are in doubt, try to involve someone for an advice. 


01:29 pm March 23, 2018

I agree with these comments in regards to verifying the incorrect behavior (if any) and then determining the root cause.  Root Cause Analysis (5 why's) will be appropriate to use on the person who complained.  If the complaint is legit, have a conversation with the developer today.  If the developer did nothing wrong, and the complainer is overly sensitive, a separate conversation needs to occur with them today.

If you live in the States, you are probably aware that many are becoming unreasonably sensitive to simple, yet trivial conversations.  I offended someone the other day by simply stating that it sounded like he had a rough night (his voice was hoarse).  

As a Scrum Master, our duty is to coach and mentor.  We help mold the culture by addressing these behaviors immediately.


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.