Forums

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. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

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.

dev team member needs to be removed
Last Post 10 May 2013 04:15 AM by Chee-Hong Hsia. 4 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Not Resolved
John Beek
New Member
New Member
Posts:10
John Beek

--
27 Apr 2013 06:04 PM
    I have a dev team member that is causing problems with the rest of the team and needs to be removed. should I as the scrum master who is a management position for removing impediments remove the individual? or should the dev team who is self managing remove the individual?

    Nitin Khanna
    New Member
    New Member
    Posts:98
    Nitin Khanna

    --
    27 Apr 2013 07:05 PM
    I would imagine the Scrum Master (SM) to be a Servant Leader, having no authority over the Dev Team.

    Is the SM managing people or something else?

    Perhaps not the answer you were looking for and one can define "management" in differing ways.

    Let's also hear from others...
    Ian Mitchell
    Veteran Member
    Veteran Member
    Posts:1556
    Ian Mitchell

    --
    27 Apr 2013 10:16 PM
    It is becoming less common these days for Scrum Masters to be line managers with hiring & firing authority. I think that's a good thing because it avoids conflicts of interest like this.

    I recently read Esther Derby using an expression like "coaching someone off the team". Since a Scrum Master is a team coach, that might be one way forward, though I admit it sounds a bit cynical.
    John Keimig
    New Member
    New Member
    Posts:1
    John Keimig

    --
    29 Apr 2013 05:40 AM
    Upon reaching the conclusion that the team member must go, I believe the Scrum Master should not be left to face this alone. It seems the proper place for Scrum Master, as servant/master, to discuss with the Product Owner and Development Team (away from the individual) the issues that are becoming problems and also discuss with the individual (away from the team) what's going well, what needs to be improved, and how to approach that improvement. The Scrum Master may also assist in fostering that improvement, through moderating discussions between the member and the team.
    As the conclusion emerges, the Scrum Master would then discuss the situation with his/her own supervisor, as the reasons for removal may involve the team member's job performance. The actual removal should be handled by those with authority over the team member's job and task assignments.
    Chee-Hong Hsia
    New Member
    New Member
    Posts:73
    Chee-Hong Hsia

    --
    10 May 2013 04:15 AM
    I agree with John and to add up on his argument:
    When a Scrum Master takes on the responsibility and remove the member from the team it will somehow affect the team dynamic. Let’s say if this kind of problem occurs again, the team will automatically look at the Scrum Master for guidance. In this case I believe the Scrum Master should act as a mediator between the team members and/or supervisors.
    You are not authorized to post a reply.


    Feedback