<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Thinking inside a bigger box - Latest Comments in Top three lessons that improved our process</title><link>http://thinkinginsideabiggerbox.disqus.com/</link><description></description><language>en</language><lastBuildDate>Mon, 25 Aug 2008 17:00:26 -0000</lastBuildDate><item><title>Re: Top three lessons that improved our process</title><link>http://www.brodwall.com/johannes/blog/2008/08/22/top-three-lessons-that-improved-our-process/#comment-1830877</link><description>I don'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't know a good way to do it, I'd personally downsize the project to 10 people. I don't know if you have any better chance of succeeding, but at least you'll fail cheaper.&lt;br&gt;&lt;br&gt;(Technically, "Whole team" is not the same as "small team", but in my experience, "small team" is important too.)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">jhannes</dc:creator><pubDate>Mon, 25 Aug 2008 17:00:26 -0000</pubDate></item><item><title>Re: Top three lessons that improved our process</title><link>http://www.brodwall.com/johannes/blog/2008/08/22/top-three-lessons-that-improved-our-process/#comment-1830423</link><description>Interesting post, I think this is very good advice. I have seen the serious problems that can be caused by not following the "Whole team"-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><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">André Rakvåg</dc:creator><pubDate>Mon, 25 Aug 2008 16:21:19 -0000</pubDate></item></channel></rss>