<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Removing Team Members</title>
	<atom:link href="http://blog.mountaingoatsoftware.com/removing-team-members/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.mountaingoatsoftware.com/removing-team-members</link>
	<description>Succeeding With Agile®</description>
	<lastBuildDate>Wed, 08 Feb 2012 15:06:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: John Coleman</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-65247</link>
		<dc:creator>John Coleman</dc:creator>
		<pubDate>Tue, 02 Feb 2010 16:41:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-65247</guid>
		<description>It&#039;s not a perfect world. I think Scrum teams needs top quartile members. I frequently coach teams and team members that have difficulty to adjusting to the reality of time boxed delivery with no-where to hide. I am a scrum master (SM) with people manager experience, and I often get delegated people management responsibility. I have had to coach good teams that went through less well performing periods shall we say. Coaching for better performance and pruning poor performance is critical to maintaining/improving velocity in my view. I think that if the scrum master smells that the team is re-storming due to a perceived non-performer, he/she must bring it to a head. If I also had people management responsibility in a SM role, I coached the perceived non-performers with fair and documented improvement plans. A unanimous recommendation from the rest of the team is helpful. But, I learnt that the scrum master must be able to use his/her own judgement to go with a majority rule team decision, if he/she agrees with it, and then take the necessary action using due process. If the SM waits for a unanimous recommendation, too much time may get lost, and the situation festers. Equally, if the &quot;non-performer&quot; is simply highlighting a dysfunctional aspect within the team/organization and becoming unpopular because of that, that dysfunctional aspect should be dealt with as efficiently as possible by the SM. Perceived non performance needs to be dealt with quickly with one important caveat. The maintenance of dignity and respect should not get lost in the process of coaching/pruning teams.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not a perfect world. I think Scrum teams needs top quartile members. I frequently coach teams and team members that have difficulty to adjusting to the reality of time boxed delivery with no-where to hide. I am a scrum master (SM) with people manager experience, and I often get delegated people management responsibility. I have had to coach good teams that went through less well performing periods shall we say. Coaching for better performance and pruning poor performance is critical to maintaining/improving velocity in my view. I think that if the scrum master smells that the team is re-storming due to a perceived non-performer, he/she must bring it to a head. If I also had people management responsibility in a SM role, I coached the perceived non-performers with fair and documented improvement plans. A unanimous recommendation from the rest of the team is helpful. But, I learnt that the scrum master must be able to use his/her own judgement to go with a majority rule team decision, if he/she agrees with it, and then take the necessary action using due process. If the SM waits for a unanimous recommendation, too much time may get lost, and the situation festers. Equally, if the &#8220;non-performer&#8221; is simply highlighting a dysfunctional aspect within the team/organization and becoming unpopular because of that, that dysfunctional aspect should be dealt with as efficiently as possible by the SM. Perceived non performance needs to be dealt with quickly with one important caveat. The maintenance of dignity and respect should not get lost in the process of coaching/pruning teams.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cohn</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64873</link>
		<dc:creator>Mike Cohn</dc:creator>
		<pubDate>Wed, 27 Jan 2010 19:02:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64873</guid>
		<description>Hi Pawel--
I think this is part of what I&#039;m getting at--even if a subset of the team decides they are better off without someone, I still think there needs to be a manager or similar involved to make the ultimate call. You&#039;re also right that the manager should be aware of this before it becomes a big problem. Realistically, though, most teams figure that someone is a poor fit before a manager does. But hopefully the manager figures it before the team is ready to *act* on it.</description>
		<content:encoded><![CDATA[<p>Hi Pawel&#8211;<br />
I think this is part of what I&#8217;m getting at&#8211;even if a subset of the team decides they are better off without someone, I still think there needs to be a manager or similar involved to make the ultimate call. You&#8217;re also right that the manager should be aware of this before it becomes a big problem. Realistically, though, most teams figure that someone is a poor fit before a manager does. But hopefully the manager figures it before the team is ready to *act* on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cohn</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64872</link>
		<dc:creator>Mike Cohn</dc:creator>
		<pubDate>Wed, 27 Jan 2010 18:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64872</guid>
		<description>Hi Alan--
I think it depends if the team members are really taking this responsibility seriously and making the right decisions for the business/product or just making a decision to make themselves happy. I&#039;m reminded of some of the things I saw in high school where cliques would just suddenly banish someone. I remember seeing this quite a bit with my sister who would suddenly be out with one group of friends and in with another. My friends and I were all too nerdy to have any options but playing Dungeons &amp; Dragons all day sure was fun. (Actually we mostly played Chainmail, because D&amp;D hadn&#039;t even come out yet!)</description>
		<content:encoded><![CDATA[<p>Hi Alan&#8211;<br />
I think it depends if the team members are really taking this responsibility seriously and making the right decisions for the business/product or just making a decision to make themselves happy. I&#8217;m reminded of some of the things I saw in high school where cliques would just suddenly banish someone. I remember seeing this quite a bit with my sister who would suddenly be out with one group of friends and in with another. My friends and I were all too nerdy to have any options but playing Dungeons &#038; Dragons all day sure was fun. (Actually we mostly played Chainmail, because D&#038;D hadn&#8217;t even come out yet!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64859</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Wed, 27 Jan 2010 15:19:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64859</guid>
		<description>I think &quot;voting someone from the island&quot; isn&#039;t the problem of a team any more. Well, they&#039;re self-organized and so on, but if there&#039;s a conflict or a problem they can&#039;t solve by themselves it is time to call someone with authority to deal with it.

Asking a person to leave the team tells you very little about the source of the problem, let alone pointing who started it, but very much about scale of the problem.

If I were a manager of the team I would step in immediately and either look for reasons why it all came to the point where people voted off someone,what can be done to change it etc. Moving a person to another project can be a solution but it should be very well-though since it has significant impact on both sides: team (&quot;hey, we won this one, we can decide who works with us and who doesn&#039;t&quot;) and a moved person (&quot;have I just failed?&quot;). I&#039;d likely to look for other solutions.

And one more thought: if the situation came so far it is a yellow card for a manager of the team. They should know there is some problem way earlier. They should know when this was a &lt;a href=&quot;http://blog.brodzinski.com/2007/03/solve-small-problems.html&quot; rel=&quot;nofollow&quot;&gt;small issue which hasn&#039;t yet pupated into big ugly problem&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I think &#8220;voting someone from the island&#8221; isn&#8217;t the problem of a team any more. Well, they&#8217;re self-organized and so on, but if there&#8217;s a conflict or a problem they can&#8217;t solve by themselves it is time to call someone with authority to deal with it.</p>
<p>Asking a person to leave the team tells you very little about the source of the problem, let alone pointing who started it, but very much about scale of the problem.</p>
<p>If I were a manager of the team I would step in immediately and either look for reasons why it all came to the point where people voted off someone,what can be done to change it etc. Moving a person to another project can be a solution but it should be very well-though since it has significant impact on both sides: team (&#8220;hey, we won this one, we can decide who works with us and who doesn&#8217;t&#8221;) and a moved person (&#8220;have I just failed?&#8221;). I&#8217;d likely to look for other solutions.</p>
<p>And one more thought: if the situation came so far it is a yellow card for a manager of the team. They should know there is some problem way earlier. They should know when this was a <a href="http://blog.brodzinski.com/2007/03/solve-small-problems.html" rel="nofollow">small issue which hasn&#8217;t yet pupated into big ugly problem</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Skorkin</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64845</link>
		<dc:creator>Alan Skorkin</dc:creator>
		<pubDate>Wed, 27 Jan 2010 09:50:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64845</guid>
		<description>Hi Mike,

I agree that ultimately the decision regarding whether or not a particular person stays or goes must rest with the leadership. However it seems to me that if your team feels sufficiently empowered and comfortable enough to even consider the fact that they may have the power to influence if a particular person stays or goes - you&#039;re in a pretty good place as far as your team/organisational spirit/culture is concerned. Plus if the team and organisation is at a level of maturity where things such as &#039;voting someone off the island&#039; are possible, the situation is a lot more likely to be resolved amicably.</description>
		<content:encoded><![CDATA[<p>Hi Mike,</p>
<p>I agree that ultimately the decision regarding whether or not a particular person stays or goes must rest with the leadership. However it seems to me that if your team feels sufficiently empowered and comfortable enough to even consider the fact that they may have the power to influence if a particular person stays or goes &#8211; you&#8217;re in a pretty good place as far as your team/organisational spirit/culture is concerned. Plus if the team and organisation is at a level of maturity where things such as &#8216;voting someone off the island&#8217; are possible, the situation is a lot more likely to be resolved amicably.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cohn</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64829</link>
		<dc:creator>Mike Cohn</dc:creator>
		<pubDate>Wed, 27 Jan 2010 05:23:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64829</guid>
		<description>Hi Rajiv--
I think you&#039;re right that this could be particularly devastating. I think that was why Derek looked so horrible when I saw him at this conference. I&#039;ve seen plenty of people after they&#039;ve been laid off and you can&#039;t really see it just in their faces and how they hold themselves. Derek was clearly pained so that the first thing I asked him was &quot;what&#039;s wrong?&quot;</description>
		<content:encoded><![CDATA[<p>Hi Rajiv&#8211;<br />
I think you&#8217;re right that this could be particularly devastating. I think that was why Derek looked so horrible when I saw him at this conference. I&#8217;ve seen plenty of people after they&#8217;ve been laid off and you can&#8217;t really see it just in their faces and how they hold themselves. Derek was clearly pained so that the first thing I asked him was &#8220;what&#8217;s wrong?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rajiv</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64806</link>
		<dc:creator>Rajiv</dc:creator>
		<pubDate>Tue, 26 Jan 2010 21:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64806</guid>
		<description>Sigh !
Maybe its just me- but I would feel very uncomfortable voting someone out. 
It&#039;s not to say - that if someone is a misfit it is in the best of everyone&#039;s interest to make some changes.But I would rather have his or her manager take the decision.

I think it could do lots of damage to his\her psych to be voted out by the whole team

Getting laid off is bad
Getting fired is worse
Voting someone out seems to be just even far worse.

I have been laid off once.
and I can even handle being fired.
But not sure how I would handle being voted off- and I would not like to do to others what I can&#039;t handle.</description>
		<content:encoded><![CDATA[<p>Sigh !<br />
Maybe its just me- but I would feel very uncomfortable voting someone out.<br />
It&#8217;s not to say &#8211; that if someone is a misfit it is in the best of everyone&#8217;s interest to make some changes.But I would rather have his or her manager take the decision.</p>
<p>I think it could do lots of damage to his\her psych to be voted out by the whole team</p>
<p>Getting laid off is bad<br />
Getting fired is worse<br />
Voting someone out seems to be just even far worse.</p>
<p>I have been laid off once.<br />
and I can even handle being fired.<br />
But not sure how I would handle being voted off- and I would not like to do to others what I can&#8217;t handle.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The CDE model &#8211; and cultural musings &#171; Geir Hedemarks blog</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64804</link>
		<dc:creator>The CDE model &#8211; and cultural musings &#171; Geir Hedemarks blog</dc:creator>
		<pubDate>Tue, 26 Jan 2010 21:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64804</guid>
		<description>[...] Cohn has just written about removing team members. In his post, he describes something he calls the CDE model. The CDE model describes a container [...]</description>
		<content:encoded><![CDATA[<p>[...] Cohn has just written about removing team members. In his post, he describes something he calls the CDE model. The CDE model describes a container [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Cohn</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64803</link>
		<dc:creator>Mike Cohn</dc:creator>
		<pubDate>Tue, 26 Jan 2010 21:10:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64803</guid>
		<description>Hi Lisa--
It&#039;s good to hear from you, even if you are an impediment to this blog ;)

I completely agree. If we&#039;re going to say that ScrumMasters shouldn&#039;t have personnel responsibility (e.g., writing reviews, etc) they shouldn&#039;t be able to make a decision to fire someone or remove them from a team. That rightly belongs to the person&#039;s manager. So I completely agree with you on that. I would say though that if a team wants to kick someone off that the ScrumMaster is a first logical line in stopping that from happening, which is the example I gave above. The ScrumMaster can ask the team if they&#039;ve thought of other options, etc. If they have and the ScrumMaster agrees the person is an impediment then those opinions can be shared with a manager. But a Scrum who is &quot;just&quot; a ScrumMaster (e.g., not a dev director / part-time ScrumMaster) usually shouldn&#039;t be able to remove someone.

I think anyone who pushes a team to think in new ways will occasionally be told they are an impediment (to following the status quo). Knowing you as I do, I suspect that might have been your situation--in which case you were a good &quot;impediment&quot; and doing exactly what you were there to do.</description>
		<content:encoded><![CDATA[<p>Hi Lisa&#8211;<br />
It&#8217;s good to hear from you, even if you are an impediment to this blog <img src='http://blog.mountaingoatsoftware.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
<p>I completely agree. If we&#8217;re going to say that ScrumMasters shouldn&#8217;t have personnel responsibility (e.g., writing reviews, etc) they shouldn&#8217;t be able to make a decision to fire someone or remove them from a team. That rightly belongs to the person&#8217;s manager. So I completely agree with you on that. I would say though that if a team wants to kick someone off that the ScrumMaster is a first logical line in stopping that from happening, which is the example I gave above. The ScrumMaster can ask the team if they&#8217;ve thought of other options, etc. If they have and the ScrumMaster agrees the person is an impediment then those opinions can be shared with a manager. But a Scrum who is &#8220;just&#8221; a ScrumMaster (e.g., not a dev director / part-time ScrumMaster) usually shouldn&#8217;t be able to remove someone.</p>
<p>I think anyone who pushes a team to think in new ways will occasionally be told they are an impediment (to following the status quo). Knowing you as I do, I suspect that might have been your situation&#8211;in which case you were a good &#8220;impediment&#8221; and doing exactly what you were there to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Crispin</title>
		<link>http://blog.mountaingoatsoftware.com/removing-team-members/comment-page-1#comment-64802</link>
		<dc:creator>Lisa Crispin</dc:creator>
		<pubDate>Tue, 26 Jan 2010 21:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mountaingoatsoftware.com/?p=662#comment-64802</guid>
		<description>Based on my experiences in the past year, I think it should be up to a real manager, not the team and not the SM, to decide whether to remove someone from the team - or from the company. I think the team must have input, for sure, but there is a reason we have managers, and to me, this is a job for a manager to do after studying the situation and getting input from all concerned. 

I was told by a SM (not at my current company) that I was an &quot;impediment to the team&quot;. I wasn&#039;t - I was having the same issues as everyone else on the team (no working test environment in which to test the latest code), but I made the mistake (in his eyes) of raising this issue every day. I voluntarily left the team - who can work in that situation? But I don&#039;t feel it was the place of the SM to tell me this (especially in that manner!)

It&#039;s a tough decision whether to let someone go, whether from the team or from the company. I&#039;d prefer a good manager handle the situation.</description>
		<content:encoded><![CDATA[<p>Based on my experiences in the past year, I think it should be up to a real manager, not the team and not the SM, to decide whether to remove someone from the team &#8211; or from the company. I think the team must have input, for sure, but there is a reason we have managers, and to me, this is a job for a manager to do after studying the situation and getting input from all concerned. </p>
<p>I was told by a SM (not at my current company) that I was an &#8220;impediment to the team&#8221;. I wasn&#8217;t &#8211; I was having the same issues as everyone else on the team (no working test environment in which to test the latest code), but I made the mistake (in his eyes) of raising this issue every day. I voluntarily left the team &#8211; who can work in that situation? But I don&#8217;t feel it was the place of the SM to tell me this (especially in that manner!)</p>
<p>It&#8217;s a tough decision whether to let someone go, whether from the team or from the company. I&#8217;d prefer a good manager handle the situation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

