<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Triple Constraints Model</title>
	<atom:link href="http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/feed/" rel="self" type="application/rss+xml" />
	<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/</link>
	<description></description>
	<lastBuildDate>Sat, 06 Mar 2010 13:15:43 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: S Y Kumar</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-259</link>
		<dc:creator>S Y Kumar</dc:creator>
		<pubDate>Sat, 06 Mar 2010 13:15:43 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-259</guid>
		<description>Hi, from the PMP exam point of view, I think PMBOK v4 will hence forth be the reference and our answers should dwell around the 6 &#039;competing demands&#039; rather than the &#039;Triple Constraints&#039;.
Am I right? 
Some one from the PMI may kindly answer?</description>
		<content:encoded><![CDATA[<p>Hi, from the PMP exam point of view, I think PMBOK v4 will hence forth be the reference and our answers should dwell around the 6 &#8216;competing demands&#8217; rather than the &#8216;Triple Constraints&#8217;.<br />
Am I right?<br />
Some one from the PMI may kindly answer?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gene</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-258</link>
		<dc:creator>Gene</dc:creator>
		<pubDate>Fri, 05 Mar 2010 18:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-258</guid>
		<description>While SCOPE can change - it seems to me that if it is totally unrestrained, free running, then the notion of management discipline is significantly undermined, no?</description>
		<content:encoded><![CDATA[<p>While SCOPE can change &#8211; it seems to me that if it is totally unrestrained, free running, then the notion of management discipline is significantly undermined, no?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pd</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-257</link>
		<dc:creator>pd</dc:creator>
		<pubDate>Fri, 05 Mar 2010 04:29:38 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-257</guid>
		<description>I think the revision committies are splitting hairs. The original triple constraints were fine. 
• Scope includes quality, risk mgt, customer satisfaction
• Budget includes resources</description>
		<content:encoded><![CDATA[<p>I think the revision committies are splitting hairs. The original triple constraints were fine.<br />
• Scope includes quality, risk mgt, customer satisfaction<br />
• Budget includes resources</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rishikesh</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-249</link>
		<dc:creator>Rishikesh</dc:creator>
		<pubDate>Thu, 11 Feb 2010 22:56:13 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-249</guid>
		<description>Though most of the discussion above is related to PMI/PMBOK, my input here is from PRINCE2 which suggests 6 project management constraints:

Time, Cost, Quality, Scope, Risks and Benefits

If you see this same thing from Agile project management perspective, I would say that scope is pretty much a non-existant as a constraint, as scope is something that is assumed to change (due to business value/priorities)</description>
		<content:encoded><![CDATA[<p>Though most of the discussion above is related to PMI/PMBOK, my input here is from PRINCE2 which suggests 6 project management constraints:</p>
<p>Time, Cost, Quality, Scope, Risks and Benefits</p>
<p>If you see this same thing from Agile project management perspective, I would say that scope is pretty much a non-existant as a constraint, as scope is something that is assumed to change (due to business value/priorities)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chinelo Agbafo</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-241</link>
		<dc:creator>Chinelo Agbafo</dc:creator>
		<pubDate>Fri, 22 Jan 2010 14:49:49 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-241</guid>
		<description>Dear All,

I am enjoying all the inputs and there all very good stuffs. The originating thought on the TBQ concept by Darrell has brought out all these sound inputs which are very educative for very new or aspiring Project Management students like me.

Thanks

Chinelo</description>
		<content:encoded><![CDATA[<p>Dear All,</p>
<p>I am enjoying all the inputs and there all very good stuffs. The originating thought on the TBQ concept by Darrell has brought out all these sound inputs which are very educative for very new or aspiring Project Management students like me.</p>
<p>Thanks</p>
<p>Chinelo</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Project Management Triangle &#171; Project Management in the Wedding Planning Busines</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-209</link>
		<dc:creator>The Project Management Triangle &#171; Project Management in the Wedding Planning Busines</dc:creator>
		<pubDate>Wed, 28 Oct 2009 03:57:51 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-209</guid>
		<description>[...] src=&#8221;http://knolt.com/mairin/files/2009/10/triple-constraints.png&#8221; alt=&#8221;triple-constr.../&gt;One particularly helpful tool for project managers is the Project Management Triangle, which is [...]</description>
		<content:encoded><![CDATA[<p>[...] src=&#8221;http://knolt.com/mairin/files/2009/10/triple-constraints.png&#8221; alt=&#8221;triple-constr&#8230;/&gt;One particularly helpful tool for project managers is the Project Management Triangle, which is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rene Simons</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-156</link>
		<dc:creator>Rene Simons</dc:creator>
		<pubDate>Tue, 21 Jul 2009 17:25:02 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-156</guid>
		<description>The classic triple constraint was replaced by &quot;competing demands&quot; among:

- Scope
- Quality
- Schedule
- Budget
- Resources
- Risk

With Schedule, Cost, and Scope circling Risk, Quality, and Resources.</description>
		<content:encoded><![CDATA[<p>The classic triple constraint was replaced by &#8220;competing demands&#8221; among:</p>
<p>- Scope<br />
- Quality<br />
- Schedule<br />
- Budget<br />
- Resources<br />
- Risk</p>
<p>With Schedule, Cost, and Scope circling Risk, Quality, and Resources.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Randy Paul</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-155</link>
		<dc:creator>Randy Paul</dc:creator>
		<pubDate>Tue, 21 Jul 2009 17:09:44 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-155</guid>
		<description>The triple constraints I learned were a triangle made up of time, cost and quality making up the three sides or constraints. Changes to any one side would have an impact to at least one of the other two sides. While scope is a constraint within a project, changes to scope will almost always have an impact to all three of the other constraints. In other words, the size and shape of the project contained by the three constraints of time, cost, and quality are determined by the scope of the project. This concept is correctly located in the Risk section of the PMBOK. The question is: does the PMBOK adequately communicate the interdependence between the four constraints?</description>
		<content:encoded><![CDATA[<p>The triple constraints I learned were a triangle made up of time, cost and quality making up the three sides or constraints. Changes to any one side would have an impact to at least one of the other two sides. While scope is a constraint within a project, changes to scope will almost always have an impact to all three of the other constraints. In other words, the size and shape of the project contained by the three constraints of time, cost, and quality are determined by the scope of the project. This concept is correctly located in the Risk section of the PMBOK. The question is: does the PMBOK adequately communicate the interdependence between the four constraints?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-153</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Mon, 20 Jul 2009 15:57:48 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-153</guid>
		<description>Actually a better reference in the PMBOK v4 is P6 which lists the 6 competing project constraints:

- Scope
- Budget
- Schedule
- Risk
- Quality
- Resources

While PMBOK v3 does refer to the triple constraint of Scope, Budget, Schedule (p8), most training materials and sample questions will also cover the &quot;alternate triangle&quot; of Risk, Quality, Resources.

I think this evolution of the &quot;triple constraint&quot;, since in today&#039;s highly competitive environment the 3 constraints is just too simplistic.</description>
		<content:encoded><![CDATA[<p>Actually a better reference in the PMBOK v4 is P6 which lists the 6 competing project constraints:</p>
<p>- Scope<br />
- Budget<br />
- Schedule<br />
- Risk<br />
- Quality<br />
- Resources</p>
<p>While PMBOK v3 does refer to the triple constraint of Scope, Budget, Schedule (p8), most training materials and sample questions will also cover the &#8220;alternate triangle&#8221; of Risk, Quality, Resources.</p>
<p>I think this evolution of the &#8220;triple constraint&#8221;, since in today&#8217;s highly competitive environment the 3 constraints is just too simplistic.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kurt J. Clemente Sr., PMP</title>
		<link>http://projectmanagementblog.globalknowledge.com/2009/06/01/triple-constraints-model/#comment-152</link>
		<dc:creator>Kurt J. Clemente Sr., PMP</dc:creator>
		<pubDate>Mon, 20 Jul 2009 14:50:20 +0000</pubDate>
		<guid isPermaLink="false">http://projectmanagementblog.globalknowledge.com/?p=210#comment-152</guid>
		<description>As we teach project management principles to today&#039;s new project managers, we need to take off the blinders and realize that tomorrow&#039;s modern project manager needs to come to grip with more than just the traditional &quot;triple constraints&quot;, plus Quality.  

Realistically, we will always be pounded on by stakeholders for schedule (time), budget (cost) and scope. And now, PMI has finally placed Quality on the same playing level as time, cost and scope. For what is the point of bringing a project in on time, on budget, and within scope if what you deliver is a piece of crap.

But, now we propose that 2 more priorities be given &quot;equal&quot; weight.  One is Risk.  We typically draw a circle around the triple constraints and label the circle &quot;Risk&quot;, as risk pushes on all three sides of the triple constraints.  The second proposed priority is customer satisfaction.  After all, happy customers are repeat customer, and repeat customers put dollars in the bank.  And when the day is over, it is really all about the money.

We are now using a 6-sided figure to represent the priorities that face us in our projects. So, on time, within budget, within scope, good quality, manage the risks that can crush your project, and achieve customer satisfaction; these are the revised priorities that face today&#039;s modern project manager.</description>
		<content:encoded><![CDATA[<p>As we teach project management principles to today&#8217;s new project managers, we need to take off the blinders and realize that tomorrow&#8217;s modern project manager needs to come to grip with more than just the traditional &#8220;triple constraints&#8221;, plus Quality.  </p>
<p>Realistically, we will always be pounded on by stakeholders for schedule (time), budget (cost) and scope. And now, PMI has finally placed Quality on the same playing level as time, cost and scope. For what is the point of bringing a project in on time, on budget, and within scope if what you deliver is a piece of crap.</p>
<p>But, now we propose that 2 more priorities be given &#8220;equal&#8221; weight.  One is Risk.  We typically draw a circle around the triple constraints and label the circle &#8220;Risk&#8221;, as risk pushes on all three sides of the triple constraints.  The second proposed priority is customer satisfaction.  After all, happy customers are repeat customer, and repeat customers put dollars in the bank.  And when the day is over, it is really all about the money.</p>
<p>We are now using a 6-sided figure to represent the priorities that face us in our projects. So, on time, within budget, within scope, good quality, manage the risks that can crush your project, and achieve customer satisfaction; these are the revised priorities that face today&#8217;s modern project manager.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
