<?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: Three Thinking Gems for Software Development Projects</title>
	<atom:link href="http://blog.martinig.ch/software-development/three-thinking-gems-for-software-development-projects/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.martinig.ch/software-development/three-thinking-gems-for-software-development-projects/</link>
	<description></description>
	<lastBuildDate>Thu, 12 Aug 2010 22:59:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Editor</title>
		<link>http://blog.martinig.ch/software-development/three-thinking-gems-for-software-development-projects/comment-page-1/#comment-7920</link>
		<dc:creator>The Editor</dc:creator>
		<pubDate>Thu, 05 Feb 2009 11:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martinig.ch/?p=226#comment-7920</guid>
		<description>Yes, there are large projects and large teams. After the first quote, Larman and Vodde explain that large, multisite and offshore projects are going to happen. How to handle them is discussed in this book and a companion book focused on practices on scaling agile software development.</description>
		<content:encoded><![CDATA[<p>Yes, there are large projects and large teams. After the first quote, Larman and Vodde explain that large, multisite and offshore projects are going to happen. How to handle them is discussed in this book and a companion book focused on practices on scaling agile software development.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gareth Hill</title>
		<link>http://blog.martinig.ch/software-development/three-thinking-gems-for-software-development-projects/comment-page-1/#comment-7916</link>
		<dc:creator>Gareth Hill</dc:creator>
		<pubDate>Thu, 05 Feb 2009 09:53:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.martinig.ch/?p=226#comment-7916</guid>
		<description>This is interesting. I am a relatively young developer/analyst and now that I have several post-university years of experience I recently thought I would revisit Brooks&#039; Mythical Man Month which we studied but I did not take too much notice of at the time! In the Surgical Team chapter I was surprised to see the suggestion that young managers want a small sharp team, but you can&#039;t build a very large system this way. I thought maybe there is something I need to learn from this and I am naive, as my experiences so far has made me think that I would always favour a &quot;small group of great people&quot; for a project of any size. A project which needs to involve a huge team I would be very hesitant about managing or being part of as it would seem so unproductive and difficult to coordinate. Maybe there are projects where a large team is necessary?</description>
		<content:encoded><![CDATA[<p>This is interesting. I am a relatively young developer/analyst and now that I have several post-university years of experience I recently thought I would revisit Brooks&#8217; Mythical Man Month which we studied but I did not take too much notice of at the time! In the Surgical Team chapter I was surprised to see the suggestion that young managers want a small sharp team, but you can&#8217;t build a very large system this way. I thought maybe there is something I need to learn from this and I am naive, as my experiences so far has made me think that I would always favour a &#8220;small group of great people&#8221; for a project of any size. A project which needs to involve a huge team I would be very hesitant about managing or being part of as it would seem so unproductive and difficult to coordinate. Maybe there are projects where a large team is necessary?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
