<?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: Choosing The Task to Fit The Time</title>
	<atom:link href="http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/</link>
	<description>Working To Live</description>
	<lastBuildDate>Tue, 28 Nov 2006 15:04:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Harmony</title>
		<link>http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/comment-page-1/#comment-925</link>
		<dc:creator>Harmony</dc:creator>
		<pubDate>Tue, 18 Oct 2005 02:12:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/#comment-925</guid>
		<description>I actually just finished reading a good article on this topic - &#039;Painless Software Schedules&#039; by Joel on Software: http://www.joelonsoftware.com/articles/fog0000000245.html

It&#039;s useful stuff because it allows you to plot a project out from the very start, with every little piece estimated in hours, so if your manager (or client) says &quot;do it faster&quot; you can point to the schedule and say &quot;not possible, but here&#039;s a heap of fluff features we can scratch or postpone if you want to pull the release date forward&quot;.</description>
		<content:encoded><![CDATA[<p>I actually just finished reading a good article on this topic &#8211; &#8216;Painless Software Schedules&#8217; by Joel on Software: <a href="http://www.joelonsoftware.com/articles/fog0000000245.html" rel="nofollow">http://www.joelonsoftware.com/.....00245.html</a></p>
<p>It&#8217;s useful stuff because it allows you to plot a project out from the very start, with every little piece estimated in hours, so if your manager (or client) says &#8220;do it faster&#8221; you can point to the schedule and say &#8220;not possible, but here&#8217;s a heap of fluff features we can scratch or postpone if you want to pull the release date forward&#8221;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elisa Camahort</title>
		<link>http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/comment-page-1/#comment-820</link>
		<dc:creator>Elisa Camahort</dc:creator>
		<pubDate>Tue, 04 Oct 2005 16:57:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/#comment-820</guid>
		<description>Equally common is when a client thinks of something else they&#039;d like done, and then can&#039;t grasp that they either have to increase the budget, or drop a different part of the scope of work to accommodate the new task. The main thing I find is that the &quot;give &#039;em an inch, they&#039;ll take a mile&quot; philosophy is really true, and it takes discipline to stick to what you know is the right quote, the right promise.  </description>
		<content:encoded><![CDATA[<p>Equally common is when a client thinks of something else they&#8217;d like done, and then can&#8217;t grasp that they either have to increase the budget, or drop a different part of the scope of work to accommodate the new task. The main thing I find is that the &#8220;give &#8216;em an inch, they&#8217;ll take a mile&#8221; philosophy is really true, and it takes discipline to stick to what you know is the right quote, the right promise.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Russell</title>
		<link>http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/comment-page-1/#comment-803</link>
		<dc:creator>Russell</dc:creator>
		<pubDate>Fri, 30 Sep 2005 19:22:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/#comment-803</guid>
		<description>This reminds me of the oft-quoted phrase in software development (and something Irepeatedly tell my clients: &quot;Cheap, Fast, or Good.  You may choose two.&quot;  The amazing thing is how often they choose cheap and fast.</description>
		<content:encoded><![CDATA[<p>This reminds me of the oft-quoted phrase in software development (and something Irepeatedly tell my clients: &#8220;Cheap, Fast, or Good.  You may choose two.&#8221;  The amazing thing is how often they choose cheap and fast.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J Lane</title>
		<link>http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/comment-page-1/#comment-802</link>
		<dc:creator>J Lane</dc:creator>
		<pubDate>Fri, 30 Sep 2005 15:18:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/#comment-802</guid>
		<description>You could always deliver a third of the product with the understanding that the rest will get done in the timeframe you&#039;ve estimated.

What I mean is, depending on the project, you could launch a stripped down, yet functional version to begin with and then build on it.  I think the concept of v.1, v.2 is getting lost these days.  Why does a project have to be completed in it&#039;s entirety right away?  Aren&#039;t there some functional pieces that can be launched in advance to keep people happy?</description>
		<content:encoded><![CDATA[<p>You could always deliver a third of the product with the understanding that the rest will get done in the timeframe you&#8217;ve estimated.</p>
<p>What I mean is, depending on the project, you could launch a stripped down, yet functional version to begin with and then build on it.  I think the concept of v.1, v.2 is getting lost these days.  Why does a project have to be completed in it&#8217;s entirety right away?  Aren&#8217;t there some functional pieces that can be launched in advance to keep people happy?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Murray</title>
		<link>http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/comment-page-1/#comment-801</link>
		<dc:creator>Randy Murray</dc:creator>
		<pubDate>Fri, 30 Sep 2005 13:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/#comment-801</guid>
		<description>Well, there are ways to speed up long, complex projects, but they&#039;re rarely acceptable to management or the customer.  

Here&#039;s a story, probably an urban legend.  A Disney &quot;imagineer&quot; was asked how long it would take to create a new attraction and he quickly replied, &quot;two years.&quot;  When asked if he could do it quicker he said, &quot;Yes, I could do it in 16 weeks.&quot;  When asked about the difference he told them, &quot;eliminate all of the reviews, committees,  management changes, and other projects on our plate and give me the full budget up front and I can get it done in that time.&quot;  

They, of course, wouldn&#039;t do that.  I often include a &quot;customer delay&quot; into project estimates, but you know, I never estimate enough time for that. </description>
		<content:encoded><![CDATA[<p>Well, there are ways to speed up long, complex projects, but they&#8217;re rarely acceptable to management or the customer.  </p>
<p>Here&#8217;s a story, probably an urban legend.  A Disney &#8220;imagineer&#8221; was asked how long it would take to create a new attraction and he quickly replied, &#8220;two years.&#8221;  When asked if he could do it quicker he said, &#8220;Yes, I could do it in 16 weeks.&#8221;  When asked about the difference he told them, &#8220;eliminate all of the reviews, committees,  management changes, and other projects on our plate and give me the full budget up front and I can get it done in that time.&#8221;  </p>
<p>They, of course, wouldn&#8217;t do that.  I often include a &#8220;customer delay&#8221; into project estimates, but you know, I never estimate enough time for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcelo Ruiz</title>
		<link>http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/comment-page-1/#comment-800</link>
		<dc:creator>Marcelo Ruiz</dc:creator>
		<pubDate>Fri, 30 Sep 2005 12:59:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.to-done.com/2005/09/choosing-the-task-to-fit-the-time/#comment-800</guid>
		<description>Excellent article! I have faced that problem exactly a week ago. I had to estimate a project that resulted in a time of 5 months. Obviously the client wanted to kill me!!! He find it hard to belive that... some years ago, for a project like this, I would have estimated 2 months, I would have delayed it a lot and delivered a work full of bugs. It&#039;s difficult to trust project management experience for clients.</description>
		<content:encoded><![CDATA[<p>Excellent article! I have faced that problem exactly a week ago. I had to estimate a project that resulted in a time of 5 months. Obviously the client wanted to kill me!!! He find it hard to belive that&#8230; some years ago, for a project like this, I would have estimated 2 months, I would have delayed it a lot and delivered a work full of bugs. It&#8217;s difficult to trust project management experience for clients.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
