<?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: The Death of the Project Management Triangle</title>
	<atom:link href="http://www.pmhut.com/the-death-of-the-project-management-triangle/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/the-death-of-the-project-management-triangle</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 23:59:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Dan Bogstad</title>
		<link>http://www.pmhut.com/the-death-of-the-project-management-triangle/comment-page-1#comment-38857</link>
		<dc:creator>Dan Bogstad</dc:creator>
		<pubDate>Sun, 27 Mar 2011 08:28:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4090#comment-38857</guid>
		<description>I agree with Rick's idea to add in dependencies as an additional factor. Given the Agile/Scrum frameworks I would also submit that "Technical Debit" related to the "Product" is also a worthy consideration.</description>
		<content:encoded><![CDATA[<p>I agree with Rick&#8217;s idea to add in dependencies as an additional factor. Given the Agile/Scrum frameworks I would also submit that &#8220;Technical Debit&#8221; related to the &#8220;Product&#8221; is also a worthy consideration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Woods, MBA, PMP, CCP, SSBB, CPA, BSAC, CSM</title>
		<link>http://www.pmhut.com/the-death-of-the-project-management-triangle/comment-page-1#comment-37724</link>
		<dc:creator>Rick Woods, MBA, PMP, CCP, SSBB, CPA, BSAC, CSM</dc:creator>
		<pubDate>Wed, 16 Mar 2011 19:47:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4090#comment-37724</guid>
		<description>I applaud PMI for bringing more reality to the PMBOK by adding more constraints and leaving the door open for, and hope they continue that process.

One additional one not mentioned I can think of is "dependencies."

The point is that is can differ by industry, company, department, and project and a careful eveluation needs to be done to identify the unique constraints (regardless of number) for your project.</description>
		<content:encoded><![CDATA[<p>I applaud PMI for bringing more reality to the PMBOK by adding more constraints and leaving the door open for, and hope they continue that process.</p>
<p>One additional one not mentioned I can think of is &#8220;dependencies.&#8221;</p>
<p>The point is that is can differ by industry, company, department, and project and a careful eveluation needs to be done to identify the unique constraints (regardless of number) for your project.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Working With Your Project Triangle&#8217;s Flexibility - PM Hut</title>
		<link>http://www.pmhut.com/the-death-of-the-project-management-triangle/comment-page-1#comment-21527</link>
		<dc:creator>Working With Your Project Triangle&#8217;s Flexibility - PM Hut</dc:creator>
		<pubDate>Wed, 02 Jun 2010 13:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4090#comment-21527</guid>
		<description>[...] talked about how useful the project triangle (RIP: The Project Triangle) is for understanding the dynamics between scope, time, and cost on projects. Now we are going to [...]</description>
		<content:encoded><![CDATA[<p>[...] talked about how useful the project triangle (RIP: The Project Triangle) is for understanding the dynamics between scope, time, and cost on projects. Now we are going to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shim Marom</title>
		<link>http://www.pmhut.com/the-death-of-the-project-management-triangle/comment-page-1#comment-11057</link>
		<dc:creator>Shim Marom</dc:creator>
		<pubDate>Mon, 02 Nov 2009 21:44:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4090#comment-11057</guid>
		<description>I could be wrong but the only reason the 'triple constraint' concept held for so many reasons is because it was easy to incorporate it into PowerPoint presentations. Ok seriously now, there's no reason to hold-on to concepts that are blatantly incorrect. And the PMI has finally acknowledged this fact by abolishing it and recognizing that there's more to project constraints than just time, cost and scope. Good on you PMI. :)</description>
		<content:encoded><![CDATA[<p>I could be wrong but the only reason the &#8216;triple constraint&#8217; concept held for so many reasons is because it was easy to incorporate it into PowerPoint presentations. Ok seriously now, there&#8217;s no reason to hold-on to concepts that are blatantly incorrect. And the PMI has finally acknowledged this fact by abolishing it and recognizing that there&#8217;s more to project constraints than just time, cost and scope. Good on you PMI. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nenad</title>
		<link>http://www.pmhut.com/the-death-of-the-project-management-triangle/comment-page-1#comment-10963</link>
		<dc:creator>Nenad</dc:creator>
		<pubDate>Mon, 02 Nov 2009 03:05:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4090#comment-10963</guid>
		<description>Triple constraint model is good for conceptialising the relationship between time, quality and money (i.e. resources). However, I do think that this model can be further refined to incorporate an evaluative component as a fourth dimension. For example, Michael Porter suggested that doing SWOT and PEST will provide an assessment of the company relative to its internal and external enviornment. But so what? Without knowing what this means in the context of business existence i.e. to generate income equal to or greater than its outgoings, the mere statement of position is not as useful. Hence, the competitive analysis that gives meaning to the relationship between company's internal and external environments.

Consequently, PM Triangle really needs to morph into eitehr a square or a pentagon as a consequence of including variables/dimensions/components of the model than can tell us, relative to project environment, what the changes in three contstraints mean.</description>
		<content:encoded><![CDATA[<p>Triple constraint model is good for conceptialising the relationship between time, quality and money (i.e. resources). However, I do think that this model can be further refined to incorporate an evaluative component as a fourth dimension. For example, Michael Porter suggested that doing SWOT and PEST will provide an assessment of the company relative to its internal and external enviornment. But so what? Without knowing what this means in the context of business existence i.e. to generate income equal to or greater than its outgoings, the mere statement of position is not as useful. Hence, the competitive analysis that gives meaning to the relationship between company&#8217;s internal and external environments.</p>
<p>Consequently, PM Triangle really needs to morph into eitehr a square or a pentagon as a consequence of including variables/dimensions/components of the model than can tell us, relative to project environment, what the changes in three contstraints mean.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shaun Dicker</title>
		<link>http://www.pmhut.com/the-death-of-the-project-management-triangle/comment-page-1#comment-10676</link>
		<dc:creator>Shaun Dicker</dc:creator>
		<pubDate>Fri, 30 Oct 2009 02:08:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4090#comment-10676</guid>
		<description>I think that removing the triple constraint was a very wise move by the PMI. Although it was nice and novel and used in every boardroom I’ve ever been in, the triple constraint provided a skewed view on the actual constraints and impacts we need to deal with on our projects. 

Shaun Dicker
http://shaundicker.tumblr.com</description>
		<content:encoded><![CDATA[<p>I think that removing the triple constraint was a very wise move by the PMI. Although it was nice and novel and used in every boardroom I’ve ever been in, the triple constraint provided a skewed view on the actual constraints and impacts we need to deal with on our projects. </p>
<p>Shaun Dicker<br />
<a href="http://shaundicker.tumblr.com" rel="nofollow">http://shaundicker.tumblr.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dale</title>
		<link>http://www.pmhut.com/the-death-of-the-project-management-triangle/comment-page-1#comment-10671</link>
		<dc:creator>Dale</dc:creator>
		<pubDate>Fri, 30 Oct 2009 00:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4090#comment-10671</guid>
		<description>I couldn't agree more! I had a blog post about this very topic recently. http://www.daleolsonconsulting.com/blog/2009/05/24/the-triple-constraint-is-gone/</description>
		<content:encoded><![CDATA[<p>I couldn&#8217;t agree more! I had a blog post about this very topic recently. <a href="http://www.daleolsonconsulting.com/blog/2009/05/24/the-triple-constraint-is-gone/" rel="nofollow">http://www.daleolsonconsulting.com/blog/2009/05/24/the-triple-constraint-is-gone/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

