<?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: How Can We Make the Team More Productive?</title>
	<atom:link href="http://www.gettingagile.com/2007/12/23/how-can-we-make-the-team-more-productive/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gettingagile.com/2007/12/23/how-can-we-make-the-team-more-productive/</link>
	<description>with Sterling Barton</description>
	<lastBuildDate>Sun, 04 Jul 2010 16:55:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Natalie White</title>
		<link>http://www.gettingagile.com/2007/12/23/how-can-we-make-the-team-more-productive/comment-page-1/#comment-1393</link>
		<dc:creator>Natalie White</dc:creator>
		<pubDate>Sun, 04 Jul 2010 16:55:57 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/12/23/how-can-we-make-the-team-more-productive/#comment-1393</guid>
		<description>Team building is really necessary for  a very successful implementation of business plans.&quot;`-</description>
		<content:encoded><![CDATA[<p>Team building is really necessary for  a very successful implementation of business plans.&#8221;`-</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chadd K</title>
		<link>http://www.gettingagile.com/2007/12/23/how-can-we-make-the-team-more-productive/comment-page-1/#comment-57</link>
		<dc:creator>Chadd K</dc:creator>
		<pubDate>Tue, 30 Dec 2008 03:04:26 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/12/23/how-can-we-make-the-team-more-productive/#comment-57</guid>
		<description>While part of this rings true, the real problem stems from the question of &quot;why is the manager in panic mode?&quot;  This can come from a breakdown within the process itself, or by lack of commitment from the team to actually stand behind their estimates, or a failure in the system to allow for the change in estimates as the work progresses without adjusting the scope.

It is important to remember that the scope MUST change if the amount of work changes and time does not.  Adding resource may not always work.

The most common failure of a manager is to trust the estimates provided, and &quot;bank&quot; the business on that.  While estimates are guesses at best in most organizations, the reality is that those providing the estimates don&#039;t often have the discipline to stay focused on Sunny Day Scenario when creating the estimate, or simple don&#039;t do the research necessary to give the estimate validity.

The manager then has no choice but to turn to those who have proven accomplishment in delivering what was asked - by whatever means necessary.

While it is easy to try to fix blame, it is in reality the whole team that has failed.

Building a team based on trust requires the best effort of each member, manager included, always operating with the success of the other team members at all times.  If this level of commitment and trust is sustained, the team will perform better and better, and will deliver the near impossible.  If it breaks down, it is the sad responsibility of the manager to correctly identity and cull the team or as stated, &quot;remove the impediment&quot;.

Once a poisoned attitude has been established, it can be very difficult to clean up.

Signs of a problem in a team are exactly as described above.  Managers blaming.  Panic mode. Fast not right.  Owners and specialists.  These are all signs that a team is moving faster than their ability to retain integrity.  And the march of the clock always wins.  And everyone is discouraged with each other.  And the team effectively dies.

The key is to focus on the problem.  Lose the sense of criticism, either towards each other or others towards oneself.  And focus on the improvements - not the failures.  Learn, and get better.</description>
		<content:encoded><![CDATA[<p>While part of this rings true, the real problem stems from the question of &#8220;why is the manager in panic mode?&#8221;  This can come from a breakdown within the process itself, or by lack of commitment from the team to actually stand behind their estimates, or a failure in the system to allow for the change in estimates as the work progresses without adjusting the scope.</p>
<p>It is important to remember that the scope MUST change if the amount of work changes and time does not.  Adding resource may not always work.</p>
<p>The most common failure of a manager is to trust the estimates provided, and &#8220;bank&#8221; the business on that.  While estimates are guesses at best in most organizations, the reality is that those providing the estimates don&#8217;t often have the discipline to stay focused on Sunny Day Scenario when creating the estimate, or simple don&#8217;t do the research necessary to give the estimate validity.</p>
<p>The manager then has no choice but to turn to those who have proven accomplishment in delivering what was asked &#8211; by whatever means necessary.</p>
<p>While it is easy to try to fix blame, it is in reality the whole team that has failed.</p>
<p>Building a team based on trust requires the best effort of each member, manager included, always operating with the success of the other team members at all times.  If this level of commitment and trust is sustained, the team will perform better and better, and will deliver the near impossible.  If it breaks down, it is the sad responsibility of the manager to correctly identity and cull the team or as stated, &#8220;remove the impediment&#8221;.</p>
<p>Once a poisoned attitude has been established, it can be very difficult to clean up.</p>
<p>Signs of a problem in a team are exactly as described above.  Managers blaming.  Panic mode. Fast not right.  Owners and specialists.  These are all signs that a team is moving faster than their ability to retain integrity.  And the march of the clock always wins.  And everyone is discouraged with each other.  And the team effectively dies.</p>
<p>The key is to focus on the problem.  Lose the sense of criticism, either towards each other or others towards oneself.  And focus on the improvements &#8211; not the failures.  Learn, and get better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ariel</title>
		<link>http://www.gettingagile.com/2007/12/23/how-can-we-make-the-team-more-productive/comment-page-1/#comment-56</link>
		<dc:creator>Ariel</dc:creator>
		<pubDate>Wed, 26 Dec 2007 05:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/12/23/how-can-we-make-the-team-more-productive/#comment-56</guid>
		<description>I find that this happens in circumstances where bad managers are constantly missing deadlines because they are constantly in panic mode.

Panic manifests itself as valuing certain developers and not others, creating owners and specialists so that you can ensure work is completed &quot;fast&quot; and not necessarily right.

Bad managers are also creatures of habit and will therefore introduce process because something someone did once happened to have successful results. As a result bad managers will therefore prefer to introduce impediments and label them as process.

Then during the &quot;postmortem&quot; the bad manager tries to find the person to pin the blame on for missing the deadline rather than identifing and removing impediments.

We have to find a cure for bad management. Right now the only thing that seems to work is &quot;deliver on time&quot;. I am a strong advocate of removing impediments and if you have a bad manager, well then I know what the first step is ... remove &quot;the&quot; impediment.</description>
		<content:encoded><![CDATA[<p>I find that this happens in circumstances where bad managers are constantly missing deadlines because they are constantly in panic mode.</p>
<p>Panic manifests itself as valuing certain developers and not others, creating owners and specialists so that you can ensure work is completed &#8220;fast&#8221; and not necessarily right.</p>
<p>Bad managers are also creatures of habit and will therefore introduce process because something someone did once happened to have successful results. As a result bad managers will therefore prefer to introduce impediments and label them as process.</p>
<p>Then during the &#8220;postmortem&#8221; the bad manager tries to find the person to pin the blame on for missing the deadline rather than identifing and removing impediments.</p>
<p>We have to find a cure for bad management. Right now the only thing that seems to work is &#8220;deliver on time&#8221;. I am a strong advocate of removing impediments and if you have a bad manager, well then I know what the first step is &#8230; remove &#8220;the&#8221; impediment.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
