<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"	>
<channel>
	<title>Comments on: Top three lessons that improved our process</title>
	<atom:link href="http://johannesbrodwall.com/2008/08/22/top-three-lessons-that-improved-our-process/feed/" rel="self" type="application/rss+xml" />
	<link>http://johannesbrodwall.com/2008/08/22/top-three-lessons-that-improved-our-process/</link>
	<description>Johannes Brodwall&#039;s Musings on Software Architecture and Programming</description>
	<lastBuildDate>Fri, 13 Apr 2012 19:13:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Johannes Brodwall</title>
		<link>http://johannesbrodwall.com/2008/08/22/top-three-lessons-that-improved-our-process/comment-page-1/#comment-127581</link>
		<dc:creator>Johannes Brodwall</dc:creator>
		<pubDate>Tue, 26 Aug 2008 02:00:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.brodwall.com/johannes/blog/2008/08/22/top-three-lessons-that-improved-our-process/#comment-127581</guid>
		<description>I don&#039;t know any way to succeed with a single software project with 100 people. If you know a way, I would love to learn it. :-)&lt;br&gt;&lt;br&gt;If you don&#039;t know a good way to do it, I&#039;d personally downsize the project to 10 people. I don&#039;t know if you have any better chance of succeeding, but at least you&#039;ll fail cheaper.&lt;br&gt;&lt;br&gt;(Technically, &quot;Whole team&quot; is not the same as &quot;small team&quot;, but in my experience, &quot;small team&quot; is important too.)</description>
		<content:encoded><![CDATA[<p>I don&#39;t know any way to succeed with a single software project with 100 people. If you know a way, I would love to learn it. :-)</p>
<p>If you don&#39;t know a good way to do it, I&#39;d personally downsize the project to 10 people. I don&#39;t know if you have any better chance of succeeding, but at least you&#39;ll fail cheaper.</p>
<p>(Technically, &#8220;Whole team&#8221; is not the same as &#8220;small team&#8221;, but in my experience, &#8220;small team&#8221; is important too.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: André Rakvåg</title>
		<link>http://johannesbrodwall.com/2008/08/22/top-three-lessons-that-improved-our-process/comment-page-1/#comment-127580</link>
		<dc:creator>André Rakvåg</dc:creator>
		<pubDate>Tue, 26 Aug 2008 01:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.brodwall.com/johannes/blog/2008/08/22/top-three-lessons-that-improved-our-process/#comment-127580</guid>
		<description>Interesting post, I think this is very good advice. I have seen the serious problems that can be caused by not following the &quot;Whole team&quot;-principle. But can that principle be followed on projects of size, e.g. more than 100 people? Do you have any thoughts on how one can organize such projects and follow this principle?</description>
		<content:encoded><![CDATA[<p>Interesting post, I think this is very good advice. I have seen the serious problems that can be caused by not following the &#8220;Whole team&#8221;-principle. But can that principle be followed on projects of size, e.g. more than 100 people? Do you have any thoughts on how one can organize such projects and follow this principle?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jhannes</title>
		<link>http://johannesbrodwall.com/2008/08/22/top-three-lessons-that-improved-our-process/comment-page-1/#comment-84997</link>
		<dc:creator>jhannes</dc:creator>
		<pubDate>Mon, 25 Aug 2008 19:00:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.brodwall.com/johannes/blog/2008/08/22/top-three-lessons-that-improved-our-process/#comment-84997</guid>
		<description>I don&#039;t know any way to succeed with a single software project with 100 people. If you know a way, I would love to learn it. :-)&lt;br&gt;&lt;br&gt;If you don&#039;t know a good way to do it, I&#039;d personally downsize the project to 10 people. I don&#039;t know if you have any better chance of succeeding, but at least you&#039;ll fail cheaper.&lt;br&gt;&lt;br&gt;(Technically, &quot;Whole team&quot; is not the same as &quot;small team&quot;, but in my experience, &quot;small team&quot; is important too.)</description>
		<content:encoded><![CDATA[<p>I don&#39;t know any way to succeed with a single software project with 100 people. If you know a way, I would love to learn it. :-)</p>
<p>If you don&#39;t know a good way to do it, I&#39;d personally downsize the project to 10 people. I don&#39;t know if you have any better chance of succeeding, but at least you&#39;ll fail cheaper.</p>
<p>(Technically, &#8220;Whole team&#8221; is not the same as &#8220;small team&#8221;, but in my experience, &#8220;small team&#8221; is important too.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: André Rakvåg</title>
		<link>http://johannesbrodwall.com/2008/08/22/top-three-lessons-that-improved-our-process/comment-page-1/#comment-84988</link>
		<dc:creator>André Rakvåg</dc:creator>
		<pubDate>Mon, 25 Aug 2008 18:21:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.brodwall.com/johannes/blog/2008/08/22/top-three-lessons-that-improved-our-process/#comment-84988</guid>
		<description>Interesting post, I think this is very good advice. I have seen the serious problems that can be caused by not following the &quot;Whole team&quot;-principle. But can that principle be followed on projects of size, e.g. more than 100 people? Do you have any thoughts on how one can organize such projects and follow this principle?</description>
		<content:encoded><![CDATA[<p>Interesting post, I think this is very good advice. I have seen the serious problems that can be caused by not following the &#8220;Whole team&#8221;-principle. But can that principle be followed on projects of size, e.g. more than 100 people? Do you have any thoughts on how one can organize such projects and follow this principle?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

