<?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: &#8220;Good, Fast and/or Cheap&#8221;? Refuse to Choose!</title>
	<atom:link href="http://www.grokdotcom.com/index.php/2007/09/17/good-fast-andor-cheap-refuse-to-choose/feed" rel="self" type="application/rss+xml" />
	<link>http://www.grokdotcom.com/2007/09/17/good-fast-andor-cheap-refuse-to-choose/</link>
	<description>Marketing blog focused on marketing optimization, improving website conversion rates, search engine marketing, web analytics, word of mouth, etc.</description>
	<lastBuildDate>Sat, 21 Nov 2009 23:38:51 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: 8R3ND4N</title>
		<link>http://www.grokdotcom.com/2007/09/17/good-fast-andor-cheap-refuse-to-choose/comment-page-1/#comment-197786</link>
		<dc:creator>8R3ND4N</dc:creator>
		<pubDate>Mon, 17 Sep 2007 17:01:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.grokdotcom.com/2007/09/17/good-fast-andor-cheap-refuse-to-choose/#comment-197786</guid>
		<description>As a project manager in the software development world, I was taught this &#039;magic triangle&#039; of time --&gt; cost --&gt; scope, and used it often b/c it was the easiest way to get high-paid exec stakeholders to understand that they couldn&#039;t have it all.  Of course, you CAN have it all with proper design and planning.  But most stakeholders want it all mid-project--when the timelines are already slipping!  So I don&#039;t think it&#039;s a crutch, I think it&#039;s a expectation-setting tool.</description>
		<content:encoded><![CDATA[<p>As a project manager in the software development world, I was taught this &#8216;magic triangle&#8217; of time &#8211;&gt; cost &#8211;&gt; scope, and used it often b/c it was the easiest way to get high-paid exec stakeholders to understand that they couldn&#8217;t have it all.  Of course, you CAN have it all with proper design and planning.  But most stakeholders want it all mid-project&#8211;when the timelines are already slipping!  So I don&#8217;t think it&#8217;s a crutch, I think it&#8217;s a expectation-setting tool.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
