<?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: The 4 Phases of Implementation</title>
	<atom:link href="http://www.codesqueeze.com/the-4-phases-of-implementation/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.codesqueeze.com/the-4-phases-of-implementation/</link>
	<description>Ideas for building efficient developers and software</description>
	<lastBuildDate>Fri, 12 Mar 2010 12:19:55 +0000</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: Scott Sehlhorst</title>
		<link>http://www.codesqueeze.com/the-4-phases-of-implementation/#comment-328</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Wed, 26 Sep 2007 12:50:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-4-phases-of-implementation/#comment-328</guid>
		<description>Great article, Max.  I would add that the &#039;estimate amount of remaining work&#039; step also involves communication with the team (and external stakeholders) about the nearness of goals and objectives.  Think about it in terms of running a race - you focus on how close you are to the finish line, not how far you are from the starting blocks.

Thanks for the reference, keep up the good.

Also - love the magic-eye reference, Chip!</description>
		<content:encoded><![CDATA[<p>Great article, Max.  I would add that the &#8216;estimate amount of remaining work&#8217; step also involves communication with the team (and external stakeholders) about the nearness of goals and objectives.  Think about it in terms of running a race &#8211; you focus on how close you are to the finish line, not how far you are from the starting blocks.</p>
<p>Thanks for the reference, keep up the good.</p>
<p>Also &#8211; love the magic-eye reference, Chip!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chip Overclock</title>
		<link>http://www.codesqueeze.com/the-4-phases-of-implementation/#comment-327</link>
		<dc:creator>Chip Overclock</dc:creator>
		<pubDate>Wed, 26 Sep 2007 12:07:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.codesqueeze.com/the-4-phases-of-implementation/#comment-327</guid>
		<description>I&#039;ve always likened large development projects to those &quot;magic eye&quot; pictures: they seem utter chaos then suddenly they come into focus and you see dolphins flying in space or something other silly thing. Projects over the past decade have been that way to me: iteration after iteration, bug fix after bug fix, meeting after meeting, and then they come into focus and you ship. To be fair, the project manager has a better vision of project progress than I do, with my arms in code up to my shoulders and thinking more about the current iteration than the big picture.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve always likened large development projects to those &#8220;magic eye&#8221; pictures: they seem utter chaos then suddenly they come into focus and you see dolphins flying in space or something other silly thing. Projects over the past decade have been that way to me: iteration after iteration, bug fix after bug fix, meeting after meeting, and then they come into focus and you ship. To be fair, the project manager has a better vision of project progress than I do, with my arms in code up to my shoulders and thinking more about the current iteration than the big picture.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
