<?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: Executive questions, IT answers, pizza parlors, and speed chess</title>
	<atom:link href="http://www.peterkretzman.com/2008/05/24/executive-questions-it-answers-pizza-parlors-and-speed-chess/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.peterkretzman.com/2008/05/24/executive-questions-it-answers-pizza-parlors-and-speed-chess/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=executive-questions-it-answers-pizza-parlors-and-speed-chess</link>
	<description>Intensely practical tips on information technology management, by Peter Kretzman</description>
	<lastBuildDate>Thu, 02 Feb 2012 16:24:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: jfbauer</title>
		<link>http://www.peterkretzman.com/2008/05/24/executive-questions-it-answers-pizza-parlors-and-speed-chess/comment-page-1/#comment-9455</link>
		<dc:creator>jfbauer</dc:creator>
		<pubDate>Thu, 21 Oct 2010 10:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.peterkretzman.com/2008/05/24/executive-questions-it-answers-pizza-parlors-and-speed-chess/#comment-9455</guid>
		<description>One of the key elements of success that jumps out at me in your article is having an organizational culture that can support/accept/tolerate the element of playing speed chess: that &quot;estimates will be wildly wrong at least 30% of the time&quot;.  Based on an IT work estimate, the business starts forming plans to roll-out marketing campaigns, train call center staff/customers, change business processes and mostly likely, string these together to form their post-IT implementation master plan.  The business needs to be cognizant that their master plan needs to account for late (and even sometimes early) IT delivery dates.  Thus, IT work estimation  continues to be part art and science.  I&#039;ve written previously at the art side, here: http://bit.ly/90xVMk.  More recently, I&#039;ve written about the science side here: http://bit.ly/9BFf18.

Great post Peter!</description>
		<content:encoded><![CDATA[<p>One of the key elements of success that jumps out at me in your article is having an organizational culture that can support/accept/tolerate the element of playing speed chess: that &#8220;estimates will be wildly wrong at least 30% of the time&#8221;.  Based on an IT work estimate, the business starts forming plans to roll-out marketing campaigns, train call center staff/customers, change business processes and mostly likely, string these together to form their post-IT implementation master plan.  The business needs to be cognizant that their master plan needs to account for late (and even sometimes early) IT delivery dates.  Thus, IT work estimation  continues to be part art and science.  I&#8217;ve written previously at the art side, here: <a href="http://bit.ly/90xVMk" rel="nofollow">http://bit.ly/90xVMk</a>.  More recently, I&#8217;ve written about the science side here: <a href="http://bit.ly/9BFf18" rel="nofollow">http://bit.ly/9BFf18</a>.</p>
<p>Great post Peter!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

