<?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: Escalation is Killing our Healthy Conflict in Agile</title>
	<atom:link href="http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/</link>
	<description>Adopt, Scale and Succeed with Agile Development</description>
	<lastBuildDate>Tue, 10 Jan 2012 03:30:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Jonny Wilkinson</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4908</link>
		<dc:creator>Jonny Wilkinson</dc:creator>
		<pubDate>Tue, 08 Dec 2009 21:54:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4908</guid>
		<description>Wow ! What a great comment from Regina !

One thing I found particularly interesting is your comment...

What we saw, ..., is that people who are accustomed to being “right” for a living ... are less likely to try to find a mutually satisfactory solution.

Asking one of &quot;those people&quot; might elicit the response... &quot;I&#039;m not good at stroking people&#039;s egos.&quot; :-(

What I think that means is, &quot;I don&#039;t think it is right to compromise on a solution in order to stroke someone&#039;s ego, especially if think they didn&#039;t contribute significantly to the solution.&quot;.</description>
		<content:encoded><![CDATA[<p>Wow ! What a great comment from Regina !</p>
<p>One thing I found particularly interesting is your comment&#8230;</p>
<p>What we saw, &#8230;, is that people who are accustomed to being “right” for a living &#8230; are less likely to try to find a mutually satisfactory solution.</p>
<p>Asking one of &#8220;those people&#8221; might elicit the response&#8230; &#8220;I&#8217;m not good at stroking people&#8217;s egos.&#8221; :-(</p>
<p>What I think that means is, &#8220;I don&#8217;t think it is right to compromise on a solution in order to stroke someone&#8217;s ego, especially if think they didn&#8217;t contribute significantly to the solution.&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sameh Zeid</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4906</link>
		<dc:creator>Sameh Zeid</dc:creator>
		<pubDate>Tue, 08 Dec 2009 16:11:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4906</guid>
		<description>I always feel like our projects are bound to have escalations. In traditional project management, escalation is a formal process and can be part of the project management plan. Moreover, I found people escalate more often without following this process. 
In the agile world, where every one required for the project should be part of the team, I found escalation still happens. 
Dr. Deming has a point called &quot;Drive out fear&quot; that he incorporated into his 14 management points when he has returned back home from Japan. I think we escalate because of fear. Another point he added also was &quot;Respect to people&quot;. He said in Japan a junior engineer can stop the line and management trust her that she is doing the right thing. From my view, this action is combination of respect and no fear. Such actions come from people who continuously think of ideas for improvement and have sense of urgency.  They work within a system that not only protect them, but trust them!
By not understanding these two points we are bound to escalate. Sometimes a manager may feel pride when he receives escalations. It increases his sense of security. We escalate to survive. We escalate because of lack of respect to other people. Even if it&#039;s winning, it is very short term. Then, the project probably starts its death march.
To mitigate escalation, I think the project team should under-go training on the process (Scrum, Agile, XP…). The process should not be tweaked as this can form a bias that can increase the intensity of conflict and lead to escalations. The rules of engagement of the team members and appreciation of the interactions as required by the process can help to acknowledge each other more.</description>
		<content:encoded><![CDATA[<p>I always feel like our projects are bound to have escalations. In traditional project management, escalation is a formal process and can be part of the project management plan. Moreover, I found people escalate more often without following this process.<br />
In the agile world, where every one required for the project should be part of the team, I found escalation still happens.<br />
Dr. Deming has a point called &#8220;Drive out fear&#8221; that he incorporated into his 14 management points when he has returned back home from Japan. I think we escalate because of fear. Another point he added also was &#8220;Respect to people&#8221;. He said in Japan a junior engineer can stop the line and management trust her that she is doing the right thing. From my view, this action is combination of respect and no fear. Such actions come from people who continuously think of ideas for improvement and have sense of urgency.  They work within a system that not only protect them, but trust them!<br />
By not understanding these two points we are bound to escalate. Sometimes a manager may feel pride when he receives escalations. It increases his sense of security. We escalate to survive. We escalate because of lack of respect to other people. Even if it&#8217;s winning, it is very short term. Then, the project probably starts its death march.<br />
To mitigate escalation, I think the project team should under-go training on the process (Scrum, Agile, XP…). The process should not be tweaked as this can form a bias that can increase the intensity of conflict and lead to escalations. The rules of engagement of the team members and appreciation of the interactions as required by the process can help to acknowledge each other more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4901</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Mon, 07 Dec 2009 20:56:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4901</guid>
		<description>Lisa,

It is so cool that you see your enthusiasm as a potential threat to the team despite your wanting to use it as a gift for the team. I think allowing all voices in the room and divergence can build trust around trying new/different practices. It is much better than telling people that they must agree with you especially since you know you are right :-)

Jean</description>
		<content:encoded><![CDATA[<p>Lisa,</p>
<p>It is so cool that you see your enthusiasm as a potential threat to the team despite your wanting to use it as a gift for the team. I think allowing all voices in the room and divergence can build trust around trying new/different practices. It is much better than telling people that they must agree with you especially since you know you are right :-)</p>
<p>Jean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4899</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Mon, 07 Dec 2009 20:53:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4899</guid>
		<description>Thanks Dave for the examples.  

As the kid in &quot;The Sixth Sense&quot; movie says, &quot;I see dead people everywhere.&quot; Read through Regina Mullen&#039;s comment and see what resonates for you about how we may be engaging non-usefully in Agile. Whether it is about how you adopt Agile, what the &quot;right&quot; practices are, or who you are listening to, you may hear some rhetoric that pushes you up against a wall. When, like the &quot;dead people everywhere&quot;, we have this rhetoric expand and multiply, that is escalation, and that is a systemic dynamic.

So now I&#039;ll give an example not in our Agile community. Think about whatever significant relationships you have in your life. Pick one person in particular to whom you are very close. And imagine this person with whom you are deeply connected saying to you, &quot;If you REALLY loved me, you wouldn&#039;t think the way you do.&quot; What!!?!?! Yup, those exact words have been said to me. And, yup, that is a lose/lose situation even though the other person was going for the win.

Sigh,
Jean</description>
		<content:encoded><![CDATA[<p>Thanks Dave for the examples.  </p>
<p>As the kid in &#8220;The Sixth Sense&#8221; movie says, &#8220;I see dead people everywhere.&#8221; Read through Regina Mullen&#8217;s comment and see what resonates for you about how we may be engaging non-usefully in Agile. Whether it is about how you adopt Agile, what the &#8220;right&#8221; practices are, or who you are listening to, you may hear some rhetoric that pushes you up against a wall. When, like the &#8220;dead people everywhere&#8221;, we have this rhetoric expand and multiply, that is escalation, and that is a systemic dynamic.</p>
<p>So now I&#8217;ll give an example not in our Agile community. Think about whatever significant relationships you have in your life. Pick one person in particular to whom you are very close. And imagine this person with whom you are deeply connected saying to you, &#8220;If you REALLY loved me, you wouldn&#8217;t think the way you do.&#8221; What!!?!?! Yup, those exact words have been said to me. And, yup, that is a lose/lose situation even though the other person was going for the win.</p>
<p>Sigh,<br />
Jean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4898</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Mon, 07 Dec 2009 20:41:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4898</guid>
		<description>Regina,

This is such a wonderful commentary. Thank you so much for taking the time to post your perspectives. We have a great opportunity in the Agile community to learn from you about how we engage our passions. I love your observation that this Escalation dynamic may be in the Agile system if &quot;the basis for the community is a desire to consciously engage around the edges of complexity.&quot;

I want that engagement and I want that dancing on the edges of complexity. I just also want to hold myself personally accountable for how I engage. And, I respectfully ask others in our community to dance in healthy conflict as well.

This was great. Thanks!
Jean</description>
		<content:encoded><![CDATA[<p>Regina,</p>
<p>This is such a wonderful commentary. Thank you so much for taking the time to post your perspectives. We have a great opportunity in the Agile community to learn from you about how we engage our passions. I love your observation that this Escalation dynamic may be in the Agile system if &#8220;the basis for the community is a desire to consciously engage around the edges of complexity.&#8221;</p>
<p>I want that engagement and I want that dancing on the edges of complexity. I just also want to hold myself personally accountable for how I engage. And, I respectfully ask others in our community to dance in healthy conflict as well.</p>
<p>This was great. Thanks!<br />
Jean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4897</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Mon, 07 Dec 2009 20:35:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4897</guid>
		<description>Thanks Ryan,&#039;

I love that you keep going for the win/win. And yes, that is the exact opposite of the Escalation archetype. When there is a dynamic of win/lose in a discussion, I am very fearful that we ultimately devolve into a lose/lose stance and ossify. Then not only does no-one win in the discussion, but we can&#039;t get unstuck long enough to move to productivity in other areas. Now everyone really loses big time.

It can be pretty insidious. Again, thanks for reminding us that there really are positive archetypes like win/win!

Jean</description>
		<content:encoded><![CDATA[<p>Thanks Ryan,&#8217;</p>
<p>I love that you keep going for the win/win. And yes, that is the exact opposite of the Escalation archetype. When there is a dynamic of win/lose in a discussion, I am very fearful that we ultimately devolve into a lose/lose stance and ossify. Then not only does no-one win in the discussion, but we can&#8217;t get unstuck long enough to move to productivity in other areas. Now everyone really loses big time.</p>
<p>It can be pretty insidious. Again, thanks for reminding us that there really are positive archetypes like win/win!</p>
<p>Jean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4896</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Mon, 07 Dec 2009 20:30:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4896</guid>
		<description>Hi Eric,

Thanks for your query. Check out Ryan Martens comment on his perspective on the Escalation archetype. Then scroll down and check out Regina Mullen&#039;s amazing comment about mediating in the Agile community and what she is seeing as some interesting behaviors.

It really does come down to having something deep within us needing to be right versus deeply wanting to gather insights and create a new set of insights. This goes back to my little 4 -step program of having an insight and presenting it for others to absorb. That&#039;s it. You can&#039;t force people to agree with you, especially not adults. That&#039;s not your job and it&#039;s not their job. :-)

Thanks, Jean</description>
		<content:encoded><![CDATA[<p>Hi Eric,</p>
<p>Thanks for your query. Check out Ryan Martens comment on his perspective on the Escalation archetype. Then scroll down and check out Regina Mullen&#8217;s amazing comment about mediating in the Agile community and what she is seeing as some interesting behaviors.</p>
<p>It really does come down to having something deep within us needing to be right versus deeply wanting to gather insights and create a new set of insights. This goes back to my little 4 -step program of having an insight and presenting it for others to absorb. That&#8217;s it. You can&#8217;t force people to agree with you, especially not adults. That&#8217;s not your job and it&#8217;s not their job. :-)</p>
<p>Thanks, Jean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lisa Crispin</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4895</link>
		<dc:creator>Lisa Crispin</dc:creator>
		<pubDate>Mon, 07 Dec 2009 20:20:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4895</guid>
		<description>I&#039;m reading this post without the context around it but find it helpful in my situation. I&#039;ve just come back to my team after 6 months working elsewhere. I have tons of new ideas for experiments I&#039;d like my team to try. Of course they are not just going to agree to everything I suggest. It&#039;s good to know that I should welcome conflict and not feel I have to &quot;win&quot;. In fact, I respect my team all the more for being thoughtful and forthcoming with their own ideas. I feel this is the best course for moving forward. Thanks, Jean!</description>
		<content:encoded><![CDATA[<p>I&#8217;m reading this post without the context around it but find it helpful in my situation. I&#8217;ve just come back to my team after 6 months working elsewhere. I have tons of new ideas for experiments I&#8217;d like my team to try. Of course they are not just going to agree to everything I suggest. It&#8217;s good to know that I should welcome conflict and not feel I have to &#8220;win&#8221;. In fact, I respect my team all the more for being thoughtful and forthcoming with their own ideas. I feel this is the best course for moving forward. Thanks, Jean!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Nicolette</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4872</link>
		<dc:creator>Dave Nicolette</dc:creator>
		<pubDate>Fri, 04 Dec 2009 17:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4872</guid>
		<description>&quot;Can you give a concrete example of where in agile something has been escalated in a win/lose situation for another agile method?&quot;

I don&#039;t mean to try and speak for Jean, but I think she may be alluding to the ongoing food-fight between proponents of Scrum and proponents of Kanban software development. I&#039;ve been thinking about that conflict recently as well, and wrote about it here, FWIW: http://www.davenicolette.net/agile/index.blog/1970014/godzilla-vs-megalon-or-scrum-vs-kanban/</description>
		<content:encoded><![CDATA[<p>&#8220;Can you give a concrete example of where in agile something has been escalated in a win/lose situation for another agile method?&#8221;</p>
<p>I don&#8217;t mean to try and speak for Jean, but I think she may be alluding to the ongoing food-fight between proponents of Scrum and proponents of Kanban software development. I&#8217;ve been thinking about that conflict recently as well, and wrote about it here, FWIW: <a href="http://www.davenicolette.net/agile/index.blog/1970014/godzilla-vs-megalon-or-scrum-vs-kanban/" rel="nofollow">http://www.davenicolette.net/agile/index.blog/1970014/godzilla-vs-megalon-or-scrum-vs-kanban/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Comment Report : &#124; ADR as Art</title>
		<link>http://www.rallydev.com/agileblog/2009/12/escalation-is-killing-our-healthy-conflict-in-agile/#comment-4868</link>
		<dc:creator>Comment Report : &#124; ADR as Art</dc:creator>
		<pubDate>Fri, 04 Dec 2009 03:00:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3618#comment-4868</guid>
		<description>[...] That&#8217;s why I felt moved to leave the following LONG (&#8230;) comment on the Agile Blog. [...]</description>
		<content:encoded><![CDATA[<p>[...] That&#8217;s why I felt moved to leave the following LONG (&#8230;) comment on the Agile Blog. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

