<?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 for Tom and Geri Scrum</title>
	<atom:link href="http://www.tomandgeriscrum.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tomandgeriscrum.com</link>
	<description>Training and Mentoring in Scrum</description>
	<lastBuildDate>Wed, 22 May 2013 05:13:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Hero by The Method Grid &#124; Tom and Geri Scrum</title>
		<link>http://www.tomandgeriscrum.com/2013/04/14/hero/#comment-6978</link>
		<dc:creator>The Method Grid &#124; Tom and Geri Scrum</dc:creator>
		<pubDate>Wed, 22 May 2013 05:13:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=444#comment-6978</guid>
		<description><![CDATA[[...] Hero is one of several methods we have of solving problems.  And, as you can tell, gentle reader, it&#8217;s not a particularly Agile method of solving problems.  Indeed, the term was originally coined in order to be used as a foil to carefully differentiate between a few standard problem-solving methods. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Hero is one of several methods we have of solving problems.  And, as you can tell, gentle reader, it&#8217;s not a particularly Agile method of solving problems.  Indeed, the term was originally coined in order to be used as a foil to carefully differentiate between a few standard problem-solving methods. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Process Trap by Tom</title>
		<link>http://www.tomandgeriscrum.com/2013/04/14/the-process-trap/#comment-6668</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 27 Apr 2013 19:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=460#comment-6668</guid>
		<description><![CDATA[The answer I was looking for was it decreases focus, but yes, Andrew captures that answer in another way.]]></description>
		<content:encoded><![CDATA[<p>The answer I was looking for was it decreases focus, but yes, Andrew captures that answer in another way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Hero by Andrew</title>
		<link>http://www.tomandgeriscrum.com/2013/04/14/hero/#comment-6615</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Mon, 22 Apr 2013 18:14:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=444#comment-6615</guid>
		<description><![CDATA[A list recounting the failures that spring from relying upon heroics would extend to heroic proportions. 

Instead, I strive for predictable, sustainable, routine teams. That&#039;s not to say the work is boring, far from it, but by making the process, governance routine, it disappears causes little if any churn, i.e. waste. Predictable supports planning and cost containment. Sustainable supports human growth and people management. 

Heroics burns teams out, rapidly builds mistrust, cynicism, and mis-communication and drastically lowers quality.

Reliance upon heroics to deliver a release is a failure of planning and management, and increases the cost to deliver in terms of quality, trust and inefficiencies.  

Unfortunately, the cult of the hero is quite well-ingrained in middle and upper management. There&#039;s a rich vein of information for an MBA case study out there around the role of the Heroic Narrative in management reporting.]]></description>
		<content:encoded><![CDATA[<p>A list recounting the failures that spring from relying upon heroics would extend to heroic proportions. </p>
<p>Instead, I strive for predictable, sustainable, routine teams. That&#8217;s not to say the work is boring, far from it, but by making the process, governance routine, it disappears causes little if any churn, i.e. waste. Predictable supports planning and cost containment. Sustainable supports human growth and people management. </p>
<p>Heroics burns teams out, rapidly builds mistrust, cynicism, and mis-communication and drastically lowers quality.</p>
<p>Reliance upon heroics to deliver a release is a failure of planning and management, and increases the cost to deliver in terms of quality, trust and inefficiencies.  </p>
<p>Unfortunately, the cult of the hero is quite well-ingrained in middle and upper management. There&#8217;s a rich vein of information for an MBA case study out there around the role of the Heroic Narrative in management reporting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Process Trap by admin</title>
		<link>http://www.tomandgeriscrum.com/2013/04/14/the-process-trap/#comment-6534</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Sun, 14 Apr 2013 18:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=460#comment-6534</guid>
		<description><![CDATA[Oh, very good :-)

Geri]]></description>
		<content:encoded><![CDATA[<p>Oh, very good <img src='http://www.tomandgeriscrum.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Geri</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Process Trap by Andrew</title>
		<link>http://www.tomandgeriscrum.com/2013/04/14/the-process-trap/#comment-6532</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Sun, 14 Apr 2013 17:52:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=460#comment-6532</guid>
		<description><![CDATA[&lt;i&gt;There is a really important reason why, care to guess what it is?&lt;/i&gt;

This!: http://dilbert.com/blog/entry/i_want_my_cheese/]]></description>
		<content:encoded><![CDATA[<p><i>There is a really important reason why, care to guess what it is?</i></p>
<p>This!: <a href="http://dilbert.com/blog/entry/i_want_my_cheese/" rel="nofollow">http://dilbert.com/blog/entry/i_want_my_cheese/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Uncertainty by Tom</title>
		<link>http://www.tomandgeriscrum.com/2012/12/21/uncertainty/#comment-3671</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sun, 06 Jan 2013 16:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=435#comment-3671</guid>
		<description><![CDATA[That is correct Sir.]]></description>
		<content:encoded><![CDATA[<p>That is correct Sir.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Uncertainty by Andrew</title>
		<link>http://www.tomandgeriscrum.com/2012/12/21/uncertainty/#comment-3282</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 28 Dec 2012 23:42:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=435#comment-3282</guid>
		<description><![CDATA[&gt; Any guess as to the source material for this post?

Warfighting!

The U.S. Marines&#039; philosophy booklet.]]></description>
		<content:encoded><![CDATA[<p>&gt; Any guess as to the source material for this post?</p>
<p>Warfighting!</p>
<p>The U.S. Marines&#8217; philosophy booklet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Power of Pairing by Andrew</title>
		<link>http://www.tomandgeriscrum.com/2012/10/19/the-power-of-pairing/#comment-584</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 25 Oct 2012 00:40:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=266#comment-584</guid>
		<description><![CDATA[And you&#039;re welcome, for introducing you to each other. :-). I love playing the Connector role.]]></description>
		<content:encoded><![CDATA[<p>And you&#8217;re welcome, for introducing you to each other. <img src='http://www.tomandgeriscrum.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> . I love playing the Connector role.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The War Floor by Tom</title>
		<link>http://www.tomandgeriscrum.com/2012/06/17/the-war-floor/#comment-501</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 19 Oct 2012 00:59:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=137#comment-501</guid>
		<description><![CDATA[Excellent analysis Andrew. I, of course, believe their are still massive productivity gains to be made way beyond even the best performing agile teams. So I am happy for a management team that really wants to advance to the next level. Of course, I&#039;ve NEVER met one. :-) 

-Tom]]></description>
		<content:encoded><![CDATA[<p>Excellent analysis Andrew. I, of course, believe their are still massive productivity gains to be made way beyond even the best performing agile teams. So I am happy for a management team that really wants to advance to the next level. Of course, I&#8217;ve NEVER met one. <img src='http://www.tomandgeriscrum.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  </p>
<p>-Tom</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The War Floor by Andrew Midkiff</title>
		<link>http://www.tomandgeriscrum.com/2012/06/17/the-war-floor/#comment-465</link>
		<dc:creator>Andrew Midkiff</dc:creator>
		<pubDate>Tue, 16 Oct 2012 14:07:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.tomandgeriscrum.com/?p=137#comment-465</guid>
		<description><![CDATA[The War Room appeals to a great many managers because there is a prevalent pattern I&#039;ve seen in management of valuing the Hero and the Heroic Effort. I have a very incomplete theory about the power of heroic narrative in management reporting that starts to explain part of the continuing dysfunction in many IT shops. It basically comes down to the relative power of reporting on a Heroic Effort Made By My Team, vs. my regular, predictable and un-dramatic team that constantly produces at an even pace. 

We all know the second team is what we all say we want, but the first team is what gets all the glory, awards and attention. At the team level, most people vastly prefer to work in the second environment, but at the management level, the incentive is all about reporting the first. You only have to look at motivational posters to see the prevalence of this sentiment. 

This may work, at first, to the benefit of agile adoption, while it&#039;s still seen as an Heroic Effort. But after a while, upper management tends to lose focus since there are no defining events that tell a compelling story. It&#039;s all so routine. In other words, there&#039;s not a whole lot requiring much &quot;management,&quot; only leadership and guidance of the product being worked on, which is more in the realm of the business stakeholders, and less glory for IT. For the IT managers, is more about process tweaking and guidance, which is much less interesting or feasible for most IT managers. 

In many organizations, it just doesn&#039;t make you look very interesting (at least to some sorts of managers) if in every management meeting all you have to report is &quot;We delivered three releases, same as last meeting, with the same amount of scope as last time.&quot; 

There&#039;s no sense of “dynamism,” no sense of “progression” or “continuous improvement” to tell a compelling story of onward and upward. 

That&#039;s why it&#039;s important that if you are the manager of one of these boring (from a Heroic perspective), predictable teams, that your story should not be one focused on the efforts of the team, but on the outcome, the progress and dynamism of the product or system. It probably also helps to keep, at least for upper management, the same trappings of the War Room, the Heroic Effort and the Looming Crisis, even if your teams are just humming along doing predictable and routine delivery of extraordinary results.]]></description>
		<content:encoded><![CDATA[<p>The War Room appeals to a great many managers because there is a prevalent pattern I&#8217;ve seen in management of valuing the Hero and the Heroic Effort. I have a very incomplete theory about the power of heroic narrative in management reporting that starts to explain part of the continuing dysfunction in many IT shops. It basically comes down to the relative power of reporting on a Heroic Effort Made By My Team, vs. my regular, predictable and un-dramatic team that constantly produces at an even pace. </p>
<p>We all know the second team is what we all say we want, but the first team is what gets all the glory, awards and attention. At the team level, most people vastly prefer to work in the second environment, but at the management level, the incentive is all about reporting the first. You only have to look at motivational posters to see the prevalence of this sentiment. </p>
<p>This may work, at first, to the benefit of agile adoption, while it&#8217;s still seen as an Heroic Effort. But after a while, upper management tends to lose focus since there are no defining events that tell a compelling story. It&#8217;s all so routine. In other words, there&#8217;s not a whole lot requiring much &#8220;management,&#8221; only leadership and guidance of the product being worked on, which is more in the realm of the business stakeholders, and less glory for IT. For the IT managers, is more about process tweaking and guidance, which is much less interesting or feasible for most IT managers. </p>
<p>In many organizations, it just doesn&#8217;t make you look very interesting (at least to some sorts of managers) if in every management meeting all you have to report is &#8220;We delivered three releases, same as last meeting, with the same amount of scope as last time.&#8221; </p>
<p>There&#8217;s no sense of “dynamism,” no sense of “progression” or “continuous improvement” to tell a compelling story of onward and upward. </p>
<p>That&#8217;s why it&#8217;s important that if you are the manager of one of these boring (from a Heroic perspective), predictable teams, that your story should not be one focused on the efforts of the team, but on the outcome, the progress and dynamism of the product or system. It probably also helps to keep, at least for upper management, the same trappings of the War Room, the Heroic Effort and the Looming Crisis, even if your teams are just humming along doing predictable and routine delivery of extraordinary results.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
