<?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: Project Selection Pitfalls to Avoid</title>
	<atom:link href="http://www.pmhut.com/project-selection-pitfalls-to-avoid/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/project-selection-pitfalls-to-avoid</link>
	<description></description>
	<pubDate>Wed, 19 Jun 2013 18:29:09 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Project Vision Statement - PM Hut</title>
		<link>http://www.pmhut.com/project-selection-pitfalls-to-avoid/comment-page-1#comment-15081</link>
		<dc:creator>Project Vision Statement - PM Hut</dc:creator>
		<pubDate>Thu, 07 Jan 2010 19:59:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4518#comment-15081</guid>
		<description>[...] order to reach a united agreement, the Project Selection Team (PST) must first establish selection criteria. Each criterion must then be assigned a specific [...]</description>
		<content:encoded><![CDATA[<p>[...] order to reach a united agreement, the Project Selection Team (PST) must first establish selection criteria. Each criterion must then be assigned a specific [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Owen Head</title>
		<link>http://www.pmhut.com/project-selection-pitfalls-to-avoid/comment-page-1#comment-14897</link>
		<dc:creator>Owen Head</dc:creator>
		<pubDate>Mon, 04 Jan 2010 23:24:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4518#comment-14897</guid>
		<description>Hi Michael,

Shouldn't it be to produce "profitable" products and services (of course quality should be a given)?

At any rate, it's worth mentioning the use of selection criteria. Written criteria can be reviewed at the start of each selection meeting to refresh everyone's memory regarding which are most important in determining which projects to take on, and to allow comments on potential changes/improvements to the criteria themselves. 

Having written criteria is nice too in that it keeps everyone on the same page with respect to the common goal. You still have to role based conflict (a good thing, I agree) to drive needed debate and follow on research. 

Good luck.</description>
		<content:encoded><![CDATA[<p>Hi Michael,</p>
<p>Shouldn&#8217;t it be to produce &#8220;profitable&#8221; products and services (of course quality should be a given)?</p>
<p>At any rate, it&#8217;s worth mentioning the use of selection criteria. Written criteria can be reviewed at the start of each selection meeting to refresh everyone&#8217;s memory regarding which are most important in determining which projects to take on, and to allow comments on potential changes/improvements to the criteria themselves. </p>
<p>Having written criteria is nice too in that it keeps everyone on the same page with respect to the common goal. You still have to role based conflict (a good thing, I agree) to drive needed debate and follow on research. </p>
<p>Good luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Primoz Frelih, PMP</title>
		<link>http://www.pmhut.com/project-selection-pitfalls-to-avoid/comment-page-1#comment-14883</link>
		<dc:creator>Primoz Frelih, PMP</dc:creator>
		<pubDate>Mon, 04 Jan 2010 19:02:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4518#comment-14883</guid>
		<description>Construct a wishlist of potential projects. And also add not selected projects to the wishlist register, maybe in a month or two you or the market will be ready for those ideas.</description>
		<content:encoded><![CDATA[<p>Construct a wishlist of potential projects. And also add not selected projects to the wishlist register, maybe in a month or two you or the market will be ready for those ideas.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Laura Bamberg</title>
		<link>http://www.pmhut.com/project-selection-pitfalls-to-avoid/comment-page-1#comment-14880</link>
		<dc:creator>Laura Bamberg</dc:creator>
		<pubDate>Mon, 04 Jan 2010 17:23:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4518#comment-14880</guid>
		<description>Michael, this was well-said. You covered just about all of it. Unfortunately, this happens more often than it should and it is virtually impossible to recover when it does.</description>
		<content:encoded><![CDATA[<p>Michael, this was well-said. You covered just about all of it. Unfortunately, this happens more often than it should and it is virtually impossible to recover when it does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gilad Lev-Shamur</title>
		<link>http://www.pmhut.com/project-selection-pitfalls-to-avoid/comment-page-1#comment-14872</link>
		<dc:creator>Gilad Lev-Shamur</dc:creator>
		<pubDate>Mon, 04 Jan 2010 16:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4518#comment-14872</guid>
		<description>Good points!
I will also add: conduct several project selection meetings which are not aligned and managed  by the same body- cause to resources over allocation, different cost estimation models and so.

Gilad</description>
		<content:encoded><![CDATA[<p>Good points!<br />
I will also add: conduct several project selection meetings which are not aligned and managed  by the same body- cause to resources over allocation, different cost estimation models and so.</p>
<p>Gilad</p>
]]></content:encoded>
	</item>
</channel>
</rss>
