<?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"
	>
<channel>
	<title>Comments on: Using Visualization for More Accurate Time Estimations</title>
	<atom:link href="http://jessewarden.com/2008/01/using-visualization-for-more-accurate-time-estimations.html/feed" rel="self" type="application/rss+xml" />
	<link>http://jessewarden.com/2008/01/using-visualization-for-more-accurate-time-estimations.html</link>
	<description>A blog on software development, technology, games &#038; movies.</description>
	<pubDate>Wed, 09 Jul 2008 04:29:45 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: JesterXL</title>
		<link>http://jessewarden.com/2008/01/using-visualization-for-more-accurate-time-estimations.html#comment-50402</link>
		<dc:creator>JesterXL</dc:creator>
		<pubDate>Mon, 04 Feb 2008 02:51:59 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/2008/01/using-visualization-for-more-accurate-time-estimations.html#comment-50402</guid>
		<description>Only 1 and I didn't really know I did it.  Basically, it was a fixed budget job, and I refused to do fixed budget on one particular part because it was in total chaos.  Design?  Good.  Majority of components?  Good.   Back-end?  Good.  One piece of functionality undefined?  No way... if it's subjective, I can't be held accountable for some 3rd party making up scope creep as they go along.  I gave 'em 4 hours factored into the project, and the rest was hourly.

I think, though, that just made them mitigate the risk on that part of the project, so it didn't really go over budget.  However, to me, if clearly communicate risk parts to a client, not for the sake of making money, but for the sake of keeping them within their budget, they'll appreciate it.  If it can't, that's fine because at least you're not getting screwed on the deal.</description>
		<content:encoded><![CDATA[<p>Only 1 and I didn&#8217;t really know I did it.  Basically, it was a fixed budget job, and I refused to do fixed budget on one particular part because it was in total chaos.  Design?  Good.  Majority of components?  Good.   Back-end?  Good.  One piece of functionality undefined?  No way&#8230; if it&#8217;s subjective, I can&#8217;t be held accountable for some 3rd party making up scope creep as they go along.  I gave &#8216;em 4 hours factored into the project, and the rest was hourly.</p>
<p>I think, though, that just made them mitigate the risk on that part of the project, so it didn&#8217;t really go over budget.  However, to me, if clearly communicate risk parts to a client, not for the sake of making money, but for the sake of keeping them within their budget, they&#8217;ll appreciate it.  If it can&#8217;t, that&#8217;s fine because at least you&#8217;re not getting screwed on the deal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthew Campbell</title>
		<link>http://jessewarden.com/2008/01/using-visualization-for-more-accurate-time-estimations.html#comment-49601</link>
		<dc:creator>Matthew Campbell</dc:creator>
		<pubDate>Fri, 01 Feb 2008 23:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/2008/01/using-visualization-for-more-accurate-time-estimations.html#comment-49601</guid>
		<description>Jesse, hybrid approach sounds interesting, what experiences have you had using this with clients?</description>
		<content:encoded><![CDATA[<p>Jesse, hybrid approach sounds interesting, what experiences have you had using this with clients?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ravibharathii</title>
		<link>http://jessewarden.com/2008/01/using-visualization-for-more-accurate-time-estimations.html#comment-49063</link>
		<dc:creator>ravibharathii</dc:creator>
		<pubDate>Thu, 31 Jan 2008 11:28:39 +0000</pubDate>
		<guid isPermaLink="false">http://jessewarden.com/2008/01/using-visualization-for-more-accurate-time-estimations.html#comment-49063</guid>
		<description>Nice article</description>
		<content:encoded><![CDATA[<p>Nice article</p>
]]></content:encoded>
	</item>
</channel>
</rss>
