Comments on: The Triple Constraints Model and Its Disappearance from the PMBOK http://www.pmhut.com/the-triple-constraints-model-and-its-disappearance-from-the-pmbok Thu, 24 May 2012 22:10:07 +0000 http://wordpress.org/?v=abc hourly 1 By: Kate Belzer http://www.pmhut.com/the-triple-constraints-model-and-its-disappearance-from-the-pmbok/comment-page-1#comment-9091 Kate Belzer Tue, 15 Sep 2009 15:41:59 +0000 http://www.pmhut.com/?p=3720#comment-9091 While the triple constraint diagram and associated discussion is missing from the Project Management Body of Knowledge (PMBOK) – 4th Edition, the discussion around constraints specificially mentions scope, schedule, cost and quality on numerous occasions. Interestingly enough it adds risk to the list of constraints in a few cases and when discussing measurement reporting mentions scope, cost and schedule (omitting quality). I've used this model and agree that the triple constraint is a good teaching tool and a valueable conversation with clients since most business benefits cannot be realized unless these constraints are balanced appropriately. At issue is the miriad of constraints affecting projects that must be taken into consideration and limiting the dialogue to the triple constraints may limit a project managers effectiveness. I agree that it should be included in the document, at least mentioned in the section concerning the changes associated with the latest edition and why it was dropped. I believe the PMBOK is a more comprehensive document and one that should expand a project managers view of constraints to ensure a broad view of what must be taken into consideration when managing a project. While the triple constraint diagram and associated discussion is missing from the Project Management Body of Knowledge (PMBOK) – 4th Edition, the discussion around constraints specificially mentions scope, schedule, cost and quality on numerous occasions. Interestingly enough it adds risk to the list of constraints in a few cases and when discussing measurement reporting mentions scope, cost and schedule (omitting quality).

I’ve used this model and agree that the triple constraint is a good teaching tool and a valueable conversation with clients since most business benefits cannot be realized unless these constraints are balanced appropriately. At issue is the miriad of constraints affecting projects that must be taken into consideration and limiting the dialogue to the triple constraints may limit a project managers effectiveness.

I agree that it should be included in the document, at least mentioned in the section concerning the changes associated with the latest edition and why it was dropped. I believe the PMBOK is a more comprehensive document and one that should expand a project managers view of constraints to ensure a broad view of what must be taken into consideration when managing a project.

]]> By: Giovanni Giazzon http://www.pmhut.com/the-triple-constraints-model-and-its-disappearance-from-the-pmbok/comment-page-1#comment-9077 Giovanni Giazzon Mon, 14 Sep 2009 21:51:44 +0000 http://www.pmhut.com/?p=3720#comment-9077 Hi Darrell, Although what Shim Marom said is true, I also think that the classical Triple Constraints model should be still a reference in Project Management. Scope, Time and Cost are the most tangible indicators for any project: they can be measured with accuracy. Quality is an aspect of Scope. Communication isn't tangible. Risk forsees all knowledge areas. And so on. You can say that they are the Trinity of Project Management. Best Regards, Giovanni Giazzon Hi Darrell,

Although what Shim Marom said is true, I also think that the classical Triple Constraints model should be still a reference in Project Management. Scope, Time and Cost are the most tangible indicators for any project: they can be measured with accuracy. Quality is an aspect of Scope. Communication isn’t tangible. Risk forsees all knowledge areas. And so on. You can say that they are the Trinity of Project Management.

Best Regards,
Giovanni Giazzon

]]> By: Shim Marom http://www.pmhut.com/the-triple-constraints-model-and-its-disappearance-from-the-pmbok/comment-page-1#comment-9011 Shim Marom Fri, 11 Sep 2009 22:24:46 +0000 http://www.pmhut.com/?p=3720#comment-9011 The 'Triple Constraint' was a nice but not entirely accurate novelty. It was not unusual to find references to project constraints where other dimensions, Quality in particular, were added to the mix. In fact, most PMBOK Knowledge Areas can become a constraint in one way or another. I am personally happy to see this concept disappear from the PMBOK. The ‘Triple Constraint’ was a nice but not entirely accurate novelty. It was not unusual to find references to project constraints where other dimensions, Quality in particular, were added to the mix. In fact, most PMBOK Knowledge Areas can become a constraint in one way or another. I am personally happy to see this concept disappear from the PMBOK.

]]>