<?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: Planning Before A Customer Interview Is Completed - Project Management Mistake #1</title>
	<atom:link href="http://www.pmhut.com/planning-before-a-customer-interview-is-completed-project-management-mistake-1/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/planning-before-a-customer-interview-is-completed-project-management-mistake-1</link>
	<description></description>
	<pubDate>Sun, 12 Feb 2012 06:55:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: LouisvillePM</title>
		<link>http://www.pmhut.com/planning-before-a-customer-interview-is-completed-project-management-mistake-1/comment-page-1#comment-792</link>
		<dc:creator>LouisvillePM</dc:creator>
		<pubDate>Fri, 08 Aug 2008 02:23:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/project-management-mistake-1-planning-before-a-customer-interview-is-completed#comment-792</guid>
		<description>I think that the requirements development process is much like a complicated dance between relative strangers.  Like you mentioned, most people just want to start working without any kind of plan or direction. Getting to the heart of what is really needed, by asking and asking and asking questions is the only way to go, in my opinion.</description>
		<content:encoded><![CDATA[<p>I think that the requirements development process is much like a complicated dance between relative strangers.  Like you mentioned, most people just want to start working without any kind of plan or direction. Getting to the heart of what is really needed, by asking and asking and asking questions is the only way to go, in my opinion.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

