<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Hope Is Not a Project Strategy, The Project Reformer&#8217;s e-Tip</title>
	<link>http://www.reformingprojectmanagement.com/2005/04/05/472/</link>
	<description>The magazine for the project age</description>
	<pubDate>Wed, 07 Jan 2009 08:31:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Chip Patton</title>
		<link>http://www.reformingprojectmanagement.com/2005/04/05/472/#comment-971</link>
		<pubDate>Fri, 29 Apr 2005 19:59:37 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2005/04/05/472/#comment-971</guid>
					<description>The difference between a software development project and a 19th century furring expedition in the Canadian wilderness may be significant.  Particularly, it makes perfect sense not to obtain resources up front such as test and integration personnel and equipment in a SW project, especially in the face of uncertain requirements (and they are always uncertain).  Leaving the company store without your gun because you don't plan to shoot any thing for the first few days is not an option, you can't have one Fed-Ex'ed in 4 days upstream.</description>
		<content:encoded><![CDATA[<p>The difference between a software development project and a 19th century furring expedition in the Canadian wilderness may be significant.  Particularly, it makes perfect sense not to obtain resources up front such as test and integration personnel and equipment in a SW project, especially in the face of uncertain requirements (and they are always uncertain).  Leaving the company store without your gun because you don&#8217;t plan to shoot any thing for the first few days is not an option, you can&#8217;t have one Fed-Ex&#8217;ed in 4 days upstream.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hal</title>
		<link>http://www.reformingprojectmanagement.com/2005/04/05/472/#comment-968</link>
		<pubDate>Sat, 23 Apr 2005 14:57:46 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2005/04/05/472/#comment-968</guid>
					<description>Johanna Rothman writing in Managing Product Development did a nice follow-up to this e-Tip.  She writes, "I hope for lots of things, and most of the time nothing happens, unless I work to make it happen."  Have a look: &lt;a href="http://www.jrothman.com/weblog/archive/2005_04_01_mpdarchive.html#111418371837861656" rel="nofollow"&gt;
Schedule Game #4: Hope is Our Most Important Strategy&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Johanna Rothman writing in Managing Product Development did a nice follow-up to this e-Tip.  She writes, &#8220;I hope for lots of things, and most of the time nothing happens, unless I work to make it happen.&#8221;  Have a look: <a href="http://www.jrothman.com/weblog/archive/2005_04_01_mpdarchive.html#111418371837861656" rel="nofollow"><br />
Schedule Game #4: Hope is Our Most Important Strategy</a>.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
