Skip to main content

How to handle the situation further

Last post 03:37 pm October 30, 2024 by shiva schroders
3 replies
12:48 pm October 29, 2024

Hi,

I am the lead developer and the scrum master in the team. Today we had a confusion about how to develop a story. The differents in opinions specially between me as developer and one of the other developers in the team led to a heated conversion and at points screaming match. at points the developer in question said if we don't develop it this way then I cannot work and I will go home. Now I agree that disagreements in the team are normal but as the scrum master I think that I need to have a talk about how things went with this developer. however as I was the other party in this discussion I also see a conflict of interests. Now I am wondering how to handle this situation?

Thanks in advance for your help.


07:11 pm October 29, 2024

however as I was the other party in this discussion

I don't think you were, unless there are only two Developers in the team.

What were the other Developers thinking, and what were their opinions on the matter? The Developers are all collectively accountable for work being Done.


11:34 pm October 29, 2024

The situation has several problems that are likely to make it difficult.

There are some inherent difficulties when combining the Scrum Master accountabilities with any other accountabilities. Facilitation is a vital aspect of the Scrum Master accountabilities. However, it's incredibly difficult to participate in a discussion while also facilitating that discussion. Facilitation requires, among other things, making sure that all involved parties have the ability to participate while avoiding owning the discussion. Balancing the desire, as a knowledgeable party, to contribute to the conversation is often at odds with these aspects of facilitation.

On top of this, identifying as a "lead" developer means that you have legitimate power over the other developers. The Scrum framework doesn't recognize hierarchies within a Scrum Team. Still, organizational dynamics are often at play, with various role levels or people put into lead or manager positions above the other members of the team. This power can be used to influence others, and even if not directly used, can change how communication is perceived.

Ian also brings up a good question - what about the other Developers? Unless this is a team of two, participation from the other Developers could slightly mitigate some of the issues. Ultimately, though, finding ways to reduce your participation as a Developer while still using your domain and technical knowledge to support the Scrum Master accountabilities would be better. Alternatively, finding a different Scrum Master and coach to help the team would be a good choice.


03:37 pm October 30, 2024

To answer your question Ian The other developers in the team just stopped participating and decided to stay out the discussion.

I agree with you Thomas that there should be no leads in scrum and I often when possible stay away from development and focus on scrum and helping the team grow. but there are times where my knowledge as developer is needed.


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.