<?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: Defining What a Project Is</title>
	<atom:link href="http://www.pmhut.com/defining-what-a-project-is/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/defining-what-a-project-is</link>
	<description></description>
	<pubDate>Tue, 22 May 2012 18:04:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: The Project Life Cycle - PM Hut</title>
		<link>http://www.pmhut.com/defining-what-a-project-is/comment-page-1#comment-790</link>
		<dc:creator>The Project Life Cycle - PM Hut</dc:creator>
		<pubDate>Tue, 19 Aug 2008 12:15:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/defining-what-a-project-is#comment-790</guid>
		<description>[...] Defining What a Project Is [...]</description>
		<content:encoded><![CDATA[<p>[...] Defining What a Project Is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bruce</title>
		<link>http://www.pmhut.com/defining-what-a-project-is/comment-page-1#comment-789</link>
		<dc:creator>Bruce</dc:creator>
		<pubDate>Wed, 06 Aug 2008 03:18:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/defining-what-a-project-is#comment-789</guid>
		<description>There is a movement in PM groups towards splitting &lt;b&gt;outcome&lt;/b&gt; in the diagram above into &lt;b&gt;scope&lt;/b&gt; and &lt;b&gt;quality&lt;/b&gt;. The reason for this split is to place more specific emphasis on quality in a project's outcomes and to show how changes in scope &lt;i&gt;must&lt;/i&gt; impact time and/or budget rather than compromising quality.</description>
		<content:encoded><![CDATA[<p>There is a movement in PM groups towards splitting <b>outcome</b> in the diagram above into <b>scope</b> and <b>quality</b>. The reason for this split is to place more specific emphasis on quality in a project&#8217;s outcomes and to show how changes in scope <i>must</i> impact time and/or budget rather than compromising quality.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

