<?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: Keys to Successful Project Management</title>
	<atom:link href="http://www.pmhut.com/keys-to-successful-project-management/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/keys-to-successful-project-management</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 22:46:28 +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/keys-to-successful-project-management/comment-page-1#comment-796</link>
		<dc:creator>LouisvillePM</dc:creator>
		<pubDate>Thu, 14 Aug 2008 03:08:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/keys-to-successful-project-management#comment-796</guid>
		<description>I really like that you put negotiation skills as a key soft skill for PMs.  Although its not as dramatic as going down to the local used car lot, working with users and developers to create realistic requirements is definitely a negotiation.

Listening skills, the ability to connect the dots, and then negotiation skills are keys to success within the requirements development process, in my opinion.  And projects are virtually doomed from the start, without a solid understanding of the requirements by both the user and the developer.</description>
		<content:encoded><![CDATA[<p>I really like that you put negotiation skills as a key soft skill for PMs.  Although its not as dramatic as going down to the local used car lot, working with users and developers to create realistic requirements is definitely a negotiation.</p>
<p>Listening skills, the ability to connect the dots, and then negotiation skills are keys to success within the requirements development process, in my opinion.  And projects are virtually doomed from the start, without a solid understanding of the requirements by both the user and the developer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

