<?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: Adding People To A Late Project Makes It Later</title>
	<atom:link href="http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/</link>
	<description>Ideas for building efficient developers and software</description>
	<lastBuildDate>Mon, 30 Jan 2012 11:03:44 -0500</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Staying motivated during a large project &#124; ian jenkins</title>
		<link>http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-9856</link>
		<dc:creator>Staying motivated during a large project &#124; ian jenkins</dc:creator>
		<pubDate>Mon, 01 Mar 2010 18:10:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-9856</guid>
		<description>[...] Having a massive project solely on your back is not nice and will only damage the project. By choosing a number of developers to work on the task you instantly remove the pressure of one person having to deliver. This doesn&#8217;t mean throw your whole dev team at the problem, but simply share tasks based around spare time in the developers schedule. You should determine the development team for the project at the start of the project and it is important to note that if the project is running late, adding more developers to it is not the answer. [...]</description>
		<content:encoded><![CDATA[<p>[...] Having a massive project solely on your back is not nice and will only damage the project. By choosing a number of developers to work on the task you instantly remove the pressure of one person having to deliver. This doesn&#8217;t mean throw your whole dev team at the problem, but simply share tasks based around spare time in the developers schedule. You should determine the development team for the project at the start of the project and it is important to note that if the project is running late, adding more developers to it is not the answer. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: developer.cl &#187; Archivo del weblog &#187; links for 2008-09-25</title>
		<link>http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-3404</link>
		<dc:creator>developer.cl &#187; Archivo del weblog &#187; links for 2008-09-25</dc:creator>
		<pubDate>Thu, 05 Feb 2009 14:39:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-3404</guid>
		<description>[...] Adding People To A Late Project Makes It Later (tags: management development) [...]</description>
		<content:encoded><![CDATA[<p>[...] Adding People To A Late Project Makes It Later (tags: management development) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-2803</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Fri, 12 Sep 2008 20:31:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-2803</guid>
		<description>I just had an idiot for a client pull a project because &quot;it wasnt moving as fast as they wanted it to&quot; meanwhile 6 solid weeks of work had already been put into this project and no pay had come my way.  They breached the contract and now they get no code.  Tough sh*t on them.  This and your article and all I&#039;ve seen out there goes to prove that there are multitudes more folks out there who do not know whats going on, how to run projects (especially IT projects) and so forth, than there are those folks who &quot;get it&quot;.

Its really sad.</description>
		<content:encoded><![CDATA[<p>I just had an idiot for a client pull a project because &#8220;it wasnt moving as fast as they wanted it to&#8221; meanwhile 6 solid weeks of work had already been put into this project and no pay had come my way.  They breached the contract and now they get no code.  Tough sh*t on them.  This and your article and all I&#8217;ve seen out there goes to prove that there are multitudes more folks out there who do not know whats going on, how to run projects (especially IT projects) and so forth, than there are those folks who &#8220;get it&#8221;.</p>
<p>Its really sad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arjan`s World &#187; LINKBLOG for September 10, 2008</title>
		<link>http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-2799</link>
		<dc:creator>Arjan`s World &#187; LINKBLOG for September 10, 2008</dc:creator>
		<pubDate>Thu, 11 Sep 2008 08:05:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-2799</guid>
		<description>[...] Adding People To A Late Project Makes It Later - Max Pool &#8216; There will always be a cost to new employees, so you can not always use it as an excuse not to bring on new blood - but is at the end of a project when you are the busiest the best time? &#8216; [...]</description>
		<content:encoded><![CDATA[<p>[...] Adding People To A Late Project Makes It Later &#8211; Max Pool &#8216; There will always be a cost to new employees, so you can not always use it as an excuse not to bring on new blood &#8211; but is at the end of a project when you are the busiest the best time? &#8216; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dew Drop - September 10, 2008 &#124; Alvin Ashcraft's Morning Dew</title>
		<link>http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-2797</link>
		<dc:creator>Dew Drop - September 10, 2008 &#124; Alvin Ashcraft's Morning Dew</dc:creator>
		<pubDate>Wed, 10 Sep 2008 13:11:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/adding-people-to-a-late-project-makes-it-later/#comment-2797</guid>
		<description>[...] Adding People to a Late Project Makes It Later (Max Pool) [...]</description>
		<content:encoded><![CDATA[<p>[...] Adding People to a Late Project Makes It Later (Max Pool) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

