<?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: Creating a self-organizing environment</title>
	<atom:link href="http://www.ilen.org/2009/08/creating-a-self-organizing-environment/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ilen.org/2009/08/creating-a-self-organizing-environment/</link>
	<description>A starry-eyed pragmatist tackles software development, UX and pie.</description>
	<lastBuildDate>Mon, 21 Dec 2009 23:18:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Tom</title>
		<link>http://www.ilen.org/2009/08/creating-a-self-organizing-environment/comment-page-1/#comment-3</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Thu, 06 Aug 2009 17:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.ilen.org/?p=19#comment-3</guid>
		<description>I am interested in the notion you mention about Resource abundance. As a software developer, I have always advocated the principle that &quot;less&quot; is better - bigger development teams make things harder - even for projects that seemingly require a large team approach.

In the &quot;tiger team&quot; you worked on, perhaps what would have helped the project is not solely an abundance of resources, but timing their utilization? In other words, would the results have been better with more resources assigned throughout the entire project? It seems like the concept of just-in-time may, as you state previously, be key. That it&#039;s not about staffing a project throughout its lifetime with a bunch of people, but it&#039;s about have having *flexible* folks *available* to a project that provides an environment for success. Of course implementing an ebb and flow people approach in a corporate environment seems daunting to say the least, certainly from a management buy-in perspective.</description>
		<content:encoded><![CDATA[<p>I am interested in the notion you mention about Resource abundance. As a software developer, I have always advocated the principle that &#8220;less&#8221; is better &#8211; bigger development teams make things harder &#8211; even for projects that seemingly require a large team approach.</p>
<p>In the &#8220;tiger team&#8221; you worked on, perhaps what would have helped the project is not solely an abundance of resources, but timing their utilization? In other words, would the results have been better with more resources assigned throughout the entire project? It seems like the concept of just-in-time may, as you state previously, be key. That it&#8217;s not about staffing a project throughout its lifetime with a bunch of people, but it&#8217;s about have having *flexible* folks *available* to a project that provides an environment for success. Of course implementing an ebb and flow people approach in a corporate environment seems daunting to say the least, certainly from a management buy-in perspective.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->