<?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 Agile &#8211; Can We Please Stop It?</title>
	<atom:link href="http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/</link>
	<description>Adopt, Scale and Succeed with Agile Development</description>
	<lastBuildDate>Wed, 17 Mar 2010 14:33:06 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Regina Mullen</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4869</link>
		<dc:creator>Regina Mullen</dc:creator>
		<pubDate>Fri, 04 Dec 2009 03:17:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4869</guid>
		<description>Left a long post before, so I&#039;ll keep this short. 

In one mediation, I used the imagery of sine and cosine waves to show not only information processing, but as a visual way of encouraging alignment without toooo much objective compromise.

That&#039;s why I call what I do &quot;Human Trigonometry,&quot; but I won&#039;t go into that here other than to leave the example!</description>
		<content:encoded><![CDATA[<p>Left a long post before, so I&#8217;ll keep this short. </p>
<p>In one mediation, I used the imagery of sine and cosine waves to show not only information processing, but as a visual way of encouraging alignment without toooo much objective compromise.</p>
<p>That&#8217;s why I call what I do &#8220;Human Trigonometry,&#8221; but I won&#8217;t go into that here other than to leave the example!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Benton</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4809</link>
		<dc:creator>Kevin Benton</dc:creator>
		<pubDate>Mon, 16 Nov 2009 03:24:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4809</guid>
		<description>Jean - right on.  I appreciated when I got to hear a number of your insights in person while in Denver.  What I find most challenging about *any* process improvement methodologies is the religious &quot;right&quot; (left) of those who say their way is &quot;the way&quot; versus the recognition that if there was &quot;one true path&quot; that most of us would either have already been on it.

The reality is that when anyone (myself included) who knows more than someone else has a responsibility to accept that he/she doesn&#039;t know it all and be willing to accept that there are times that the professor becomes the student.

Like most others, I welcome honest and open dialog when the time is appropriate and the intent is sincere.  The problem is, there are often times when others attempt to take advantage of a) inopportune timing, or insincerity.  In my work, I&#039;m asking to be able to help fix real problems while being able to continuing being effective at doing my job.  

My challenge has been managing my effectiveness in coaching others while getting my job done.  Coaching is something that I need to do so I have more time to coach.  Getting my job done isn&#039;t always the most effective use of my time.  It&#039;s another &quot;give the person a fish or teach them how to fish&quot; kind of thing.  The problem is, my &quot;students&quot; often would often rather I just grab a fish for them by fixing the problem at hand.</description>
		<content:encoded><![CDATA[<p>Jean &#8211; right on.  I appreciated when I got to hear a number of your insights in person while in Denver.  What I find most challenging about *any* process improvement methodologies is the religious &#8220;right&#8221; (left) of those who say their way is &#8220;the way&#8221; versus the recognition that if there was &#8220;one true path&#8221; that most of us would either have already been on it.</p>
<p>The reality is that when anyone (myself included) who knows more than someone else has a responsibility to accept that he/she doesn&#8217;t know it all and be willing to accept that there are times that the professor becomes the student.</p>
<p>Like most others, I welcome honest and open dialog when the time is appropriate and the intent is sincere.  The problem is, there are often times when others attempt to take advantage of a) inopportune timing, or insincerity.  In my work, I&#8217;m asking to be able to help fix real problems while being able to continuing being effective at doing my job.  </p>
<p>My challenge has been managing my effectiveness in coaching others while getting my job done.  Coaching is something that I need to do so I have more time to coach.  Getting my job done isn&#8217;t always the most effective use of my time.  It&#8217;s another &#8220;give the person a fish or teach them how to fish&#8221; kind of thing.  The problem is, my &#8220;students&#8221; often would often rather I just grab a fish for them by fixing the problem at hand.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4789</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Thu, 12 Nov 2009 18:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4789</guid>
		<description>Hello,

Once again, I apologize for my lack of visibility in this conversation. I am heartened by the number of people adding further meat to the &quot;dialogue bone&quot;. Recognizing the value of positive conflict through dialogue versus the downward spiral of destructive conflict is a crucial point here. Collaboration and growth invite conflict. I would not want anyone to misconstrue my comments as being anti-conflict or an attempt to encourage conflict avoidance. Rather, I seek growth through the dialogue around divergent perspectives. Divergence is critical in our work. I AM asking for a positive approach to divergence. I am asking that we actively seek MORE insights versus attacking differing insights.

Remember, escalation is: &quot;My fix is your nightmare and you have to lose in order for me to win.&quot; This is a broken system. I can&#039;t support a continued embrace of a broken system.

Finally, I am writing a follow-up post to this one to provide some further thoughts on systems thinking and the escalation model in particular.

Thanks,
Jean</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>Once again, I apologize for my lack of visibility in this conversation. I am heartened by the number of people adding further meat to the &#8220;dialogue bone&#8221;. Recognizing the value of positive conflict through dialogue versus the downward spiral of destructive conflict is a crucial point here. Collaboration and growth invite conflict. I would not want anyone to misconstrue my comments as being anti-conflict or an attempt to encourage conflict avoidance. Rather, I seek growth through the dialogue around divergent perspectives. Divergence is critical in our work. I AM asking for a positive approach to divergence. I am asking that we actively seek MORE insights versus attacking differing insights.</p>
<p>Remember, escalation is: &#8220;My fix is your nightmare and you have to lose in order for me to win.&#8221; This is a broken system. I can&#8217;t support a continued embrace of a broken system.</p>
<p>Finally, I am writing a follow-up post to this one to provide some further thoughts on systems thinking and the escalation model in particular.</p>
<p>Thanks,<br />
Jean</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Mezick</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4434</link>
		<dc:creator>Dan Mezick</dc:creator>
		<pubDate>Sat, 24 Oct 2009 23:37:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4434</guid>
		<description>We are at a defining moment in this community.

We can all lose, right now, by participating in total de-stablization and self-destruction at the level of &quot;system&quot; (aka &quot;community&quot; or &quot;group&quot;)

Alternately, we can face reality and make changes to it, by participating in the shaping of something new and great. 

Those are the two choices we face now. 

Jean calls this out; Jean is a real leader. 


I like Jean&#039;s vision and I sign up now with her to advance the work. The actions I take now are listed here:

Group Relations Note dated 10/24/2009
http://www.newtechusa.com/agileboston/notes/GroupRelations.htm

This is a note regarding my strong interest in focusing the attention of the Agile/Scrum community towards Group Relations theory, practice and conferences.

I believe if enough Agile/Scrum leaders simply do some preparation and actually attend a Group Relations conference, we can advance the Agile/Scrum work. This is achievable by raising awareness of how we act and react in often completely unconscious ways as we participate in group life.</description>
		<content:encoded><![CDATA[<p>We are at a defining moment in this community.</p>
<p>We can all lose, right now, by participating in total de-stablization and self-destruction at the level of &#8220;system&#8221; (aka &#8220;community&#8221; or &#8220;group&#8221;)</p>
<p>Alternately, we can face reality and make changes to it, by participating in the shaping of something new and great. </p>
<p>Those are the two choices we face now. </p>
<p>Jean calls this out; Jean is a real leader. </p>
<p>I like Jean&#8217;s vision and I sign up now with her to advance the work. The actions I take now are listed here:</p>
<p>Group Relations Note dated 10/24/2009<br />
<a href="http://www.newtechusa.com/agileboston/notes/GroupRelations.htm" rel="nofollow">http://www.newtechusa.com/agileboston/notes/GroupRelations.htm</a></p>
<p>This is a note regarding my strong interest in focusing the attention of the Agile/Scrum community towards Group Relations theory, practice and conferences.</p>
<p>I believe if enough Agile/Scrum leaders simply do some preparation and actually attend a Group Relations conference, we can advance the Agile/Scrum work. This is achievable by raising awareness of how we act and react in often completely unconscious ways as we participate in group life.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ricky</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4310</link>
		<dc:creator>ricky</dc:creator>
		<pubDate>Mon, 19 Oct 2009 08:13:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4310</guid>
		<description>When we as a community speak to our experiences of helping teams learn and grow, we may speak to scrum, kanban, xp, agileup, dsdm … but let us do so with respect to the process and how the process needs adjusting based on the reality of the situation vs. attacking the person for their experiential viewpoint.</description>
		<content:encoded><![CDATA[<p>When we as a community speak to our experiences of helping teams learn and grow, we may speak to scrum, kanban, xp, agileup, dsdm … but let us do so with respect to the process and how the process needs adjusting based on the reality of the situation vs. attacking the person for their experiential viewpoint.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Spayd</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4136</link>
		<dc:creator>Michael Spayd</dc:creator>
		<pubDate>Mon, 05 Oct 2009 04:48:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4136</guid>
		<description>Thanks for this very stimulating post, Jean. It clearly hit a chord.

I wanted to talk about the research of John Gottman and the importance of positivity in a community and on a team, to which your post seems to point. It was way too long for this forum, so it became its own blog post at: http://collectiveedgecoaching.com/2009/10/conflict-diversity-appreciation/ .

Thanks to all the thoughtful comments from others as well. This is a very varied community!</description>
		<content:encoded><![CDATA[<p>Thanks for this very stimulating post, Jean. It clearly hit a chord.</p>
<p>I wanted to talk about the research of John Gottman and the importance of positivity in a community and on a team, to which your post seems to point. It was way too long for this forum, so it became its own blog post at: <a href="http://collectiveedgecoaching.com/2009/10/conflict-diversity-appreciation/" rel="nofollow">http://collectiveedgecoaching.com/2009/10/conflict-diversity-appreciation/</a> .</p>
<p>Thanks to all the thoughtful comments from others as well. This is a very varied community!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ronica Roth</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4133</link>
		<dc:creator>Ronica Roth</dc:creator>
		<pubDate>Mon, 05 Oct 2009 01:33:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4133</guid>
		<description>Hear hear, Jim Highsmith.

Jean specifically pointed out valuing &quot;dialogue over debate&quot;.  I often start retrospectives with a Focus On/Off exercise from Diana and Esther&#039;s Retro book, in which we help participants think through how their own behavior and words might change if they agree to value dialogue over debate.

Meanwhile, in these comments, I read lots of people discussing the merits of &quot;good&quot; debate and &quot;bad&quot; debate. What if we don&#039;t debate at all? (Picture high school debate society, and the focus on &quot;winning&quot;.) What if we have a dialogue, with a goal of improving our collective knowledge and understanding and a goal of each having more agile practices to offer our teams? How would that change the way we conducted these exchanges?</description>
		<content:encoded><![CDATA[<p>Hear hear, Jim Highsmith.</p>
<p>Jean specifically pointed out valuing &#8220;dialogue over debate&#8221;.  I often start retrospectives with a Focus On/Off exercise from Diana and Esther&#8217;s Retro book, in which we help participants think through how their own behavior and words might change if they agree to value dialogue over debate.</p>
<p>Meanwhile, in these comments, I read lots of people discussing the merits of &#8220;good&#8221; debate and &#8220;bad&#8221; debate. What if we don&#8217;t debate at all? (Picture high school debate society, and the focus on &#8220;winning&#8221;.) What if we have a dialogue, with a goal of improving our collective knowledge and understanding and a goal of each having more agile practices to offer our teams? How would that change the way we conducted these exchanges?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Stevens</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4130</link>
		<dc:creator>Peter Stevens</dc:creator>
		<pubDate>Sun, 04 Oct 2009 15:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4130</guid>
		<description>Dear Jean,

I prefer the expression, &#039;drinking our own champagne.&#039; It kind of puts a more positive spin on it. 

It&#039;s very interesting that this discussion is happening here and not say, on scrum-development or leanagile. But since we have the Internet, everything which must be said does get said, and this discussion obviously needed to happen.

Cheers,
Peter

P.S. nice to meet you.</description>
		<content:encoded><![CDATA[<p>Dear Jean,</p>
<p>I prefer the expression, &#8216;drinking our own champagne.&#8217; It kind of puts a more positive spin on it. </p>
<p>It&#8217;s very interesting that this discussion is happening here and not say, on scrum-development or leanagile. But since we have the Internet, everything which must be said does get said, and this discussion obviously needed to happen.</p>
<p>Cheers,<br />
Peter</p>
<p>P.S. nice to meet you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jean Tabaka</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4128</link>
		<dc:creator>Jean Tabaka</dc:creator>
		<pubDate>Sun, 04 Oct 2009 06:24:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4128</guid>
		<description>Hi all!

First and foremost, I appreciate you for all your incredible insights and your willingness to share with with regard to my post. I hadn&#039;t expected the number of replies. I value you taking the time to let me know how the post impacted you.

Secondly, and very importantly, I want to apologize for my lack of engagement in the discussion. I have been dealing with extensive travel (with no internet access) and then serious network issues with my machine now that I am terra firma in Melbourne, Australia.

So please do not take my silence as ignoring or hiding from all that is being shared here. Rather, I am hoping to write another post when I have better internet access in a hope to offer more information around what I mean by escalation and what I find negative and non-useful about it. 

Finally, &quot;eating my own dog food&quot;, I hope you can hear me that I am not attempting to point any fingers at any person here. Rather, I am eager to offer a notion that concentrating on positive work, positive dialogue, and growth-oriented divergence is different and more powerful than an escalation stance. This is just systems thinking at work. I&#039;ll try to explain more of that theory and practice moving forward. Ultimately, it is up to each one of us to decide whether we are on an up escalator or not, or if we create up escalators. (Okay, that is all my terminology, so don&#039;t bother looking that up!)

Again, thanks for the many great reinforcing as well as challenging comments. I&#039;m eager to stay engaged and hope to do so once my Mac decides to let me talk to the world again. (Maybe it didn&#039;t like my post :- (</description>
		<content:encoded><![CDATA[<p>Hi all!</p>
<p>First and foremost, I appreciate you for all your incredible insights and your willingness to share with with regard to my post. I hadn&#8217;t expected the number of replies. I value you taking the time to let me know how the post impacted you.</p>
<p>Secondly, and very importantly, I want to apologize for my lack of engagement in the discussion. I have been dealing with extensive travel (with no internet access) and then serious network issues with my machine now that I am terra firma in Melbourne, Australia.</p>
<p>So please do not take my silence as ignoring or hiding from all that is being shared here. Rather, I am hoping to write another post when I have better internet access in a hope to offer more information around what I mean by escalation and what I find negative and non-useful about it. </p>
<p>Finally, &#8220;eating my own dog food&#8221;, I hope you can hear me that I am not attempting to point any fingers at any person here. Rather, I am eager to offer a notion that concentrating on positive work, positive dialogue, and growth-oriented divergence is different and more powerful than an escalation stance. This is just systems thinking at work. I&#8217;ll try to explain more of that theory and practice moving forward. Ultimately, it is up to each one of us to decide whether we are on an up escalator or not, or if we create up escalators. (Okay, that is all my terminology, so don&#8217;t bother looking that up!)</p>
<p>Again, thanks for the many great reinforcing as well as challenging comments. I&#8217;m eager to stay engaged and hope to do so once my Mac decides to let me talk to the world again. (Maybe it didn&#8217;t like my post :- (</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simon Cromarty</title>
		<link>http://www.rallydev.com/agileblog/2009/10/escalation-is-killing-agile-can-we-please-stop-it/#comment-4119</link>
		<dc:creator>Simon Cromarty</dc:creator>
		<pubDate>Sat, 03 Oct 2009 02:55:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3380#comment-4119</guid>
		<description>I felt undercurrents of some conflict within our community in Chicago a few weeks ago.
As I was a newcomer to the public side of this community I was on a high from the week&#039;s immersion.
A (then) stranger, fellow Brit and mad genius spent most of the last night of the conference teaching me to look for and navigate the hidden dangers of what on the surface appeared wonderful and simple - quite humbling.

Regardless of the motives for any commentary - whether playful conflict, flame-war or frustration, with so many onlookers and so many bright passionate people, the sudden speed and scale at which differing views becomes an escalation *is* worrying. Presenting agressive commentary without setting the stage doesn&#039;t smell very good. This is why we value face-to-face communication - we can see the smiles, frowns or tears on people&#039;s faces as they&#039;re shouting and act appropriately.

A blind mob onrush towards &quot;sides&quot; may fan the flames of what may simply start out as an expression of taste or frustration. Many of us (myself included) don&#039;t have context but are still wanting to chime in with our views and support towards people we respect. Are we adding value or just laying in the boot?

Any large community or close-knit team will face conflict - it&#039;s inevitable. The challenge is in how to spot it coming and set context, manage the conflict through, look for the underlying causes and learn together.

The selection of flavors; Agile or Lean, Scrum or Kanban - They&#039;re all ice cream, some go better together as combinations and some just taste better to individuals than others.

Given the above, where&#039;s this heading and what do we as a whole community need to observe, learn and change?</description>
		<content:encoded><![CDATA[<p>I felt undercurrents of some conflict within our community in Chicago a few weeks ago.<br />
As I was a newcomer to the public side of this community I was on a high from the week&#8217;s immersion.<br />
A (then) stranger, fellow Brit and mad genius spent most of the last night of the conference teaching me to look for and navigate the hidden dangers of what on the surface appeared wonderful and simple &#8211; quite humbling.</p>
<p>Regardless of the motives for any commentary &#8211; whether playful conflict, flame-war or frustration, with so many onlookers and so many bright passionate people, the sudden speed and scale at which differing views becomes an escalation *is* worrying. Presenting agressive commentary without setting the stage doesn&#8217;t smell very good. This is why we value face-to-face communication &#8211; we can see the smiles, frowns or tears on people&#8217;s faces as they&#8217;re shouting and act appropriately.</p>
<p>A blind mob onrush towards &#8220;sides&#8221; may fan the flames of what may simply start out as an expression of taste or frustration. Many of us (myself included) don&#8217;t have context but are still wanting to chime in with our views and support towards people we respect. Are we adding value or just laying in the boot?</p>
<p>Any large community or close-knit team will face conflict &#8211; it&#8217;s inevitable. The challenge is in how to spot it coming and set context, manage the conflict through, look for the underlying causes and learn together.</p>
<p>The selection of flavors; Agile or Lean, Scrum or Kanban &#8211; They&#8217;re all ice cream, some go better together as combinations and some just taste better to individuals than others.</p>
<p>Given the above, where&#8217;s this heading and what do we as a whole community need to observe, learn and change?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
