<?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: Managing Risks of Fixed Costs</title>
	<atom:link href="http://www.pmhut.com/managing-risks-of-fixed-costs/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/managing-risks-of-fixed-costs</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 16:04:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tanmay Vora</title>
		<link>http://www.pmhut.com/managing-risks-of-fixed-costs/comment-page-1#comment-219</link>
		<dc:creator>Tanmay Vora</dc:creator>
		<pubDate>Fri, 12 Oct 2007 09:27:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/managing-risks-of-fixed-costs#comment-219</guid>
		<description>The points mentioned here are spot on - one of the biggest risk in fixed price projects is the scope. What that means is scope should be clearly defined and then controlled. Same applies to cost as you rightly say. Calculating costs at the tail end of the project leaves a little room for corrective measures.</description>
		<content:encoded><![CDATA[<p>The points mentioned here are spot on - one of the biggest risk in fixed price projects is the scope. What that means is scope should be clearly defined and then controlled. Same applies to cost as you rightly say. Calculating costs at the tail end of the project leaves a little room for corrective measures.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

