The triple constraints model has been one of the main staples for teaching project management for as long as I can remember. The model is generally represented by a triangle with Scope on the horizontal leg, Time on the left leg, Cost or Resources on the right leg and Quality in the center of the triangle.
There are variations of the triple constraints theme and name, but the concept is generally the same. The idea has to do with priorities in a project. The stakeholder must decide, in regards to a particular deliverable, which of the three constraints of scope, time and cost is most flexible, medium flexible, and least flexible. Let’s imagine a stakeholder who decides that, for a particular deliverable, time is the most flexible, scope is medium flexible and cost is least flexible. This would mean that, if need be, they would prefer a deliverable be later than originally planned as opposed to the deliverable costing more or having fewer features.
The rule is: if one of the triple constraints is changed, it will most likely affect one or both of the other constraints in addition to affecting the quality of the deliverable. An effective way to demonstrate this concept is to say to the stakeholder, “I have three cards: better, faster, and cheaper. You can only have two cards. Which of the two cards do you want?”
Upon reviewing the Guide to the Project Management Body of Knowledge (PMBOK) – 4th Edition, which came out in December, 2008, and will be the basis of the Project Management Professional (PMP) certification test beginning June 30th, 2009, I did a search for the term “triple constraints model” and it was nowhere to be found. In fact, I couldn’t find the word “triple” in the PMBOK Guide. The closest reference I could find in the PMBOK Guide – 4th Edition to the triple constraints concept was under Risk – section 11.3, page 289. Although the triple constraints model may not be in the PMBOK, I believe it to be a Best Practice and a great tool for eliciting requirements and managing change control.
The PMBOK Guide does have many references to constraints, and rightfully so. Constraints are a major consideration in project planning and execution. I just find it odd that the PMI has left out this valuable model for teaching. What are your thoughts?
Darrell G. Stiffler, PMP® has been a member of PMI since 1998 and received his PMP designation in September of 1999, a time when there were only 12,000 PMP’s in the world. He is also certified in ITIL Foundations v2 & v3. He has over 20 years of project management experience in various industries with the preponderance of his experience in IT related projects. He has consulted with both large and small organizations: General Motors; Xerox; Exel Logistic; VisionTek; Wellington Management; Boeing; General Dynamics. He has a military background and currently applies his years of experience to train and consult others in project management and ITIL professional development. He can be reached at DGStiffler at Verizon dot net.
This article was originally published in Global Knowledge’s Project Management Blog. Global Knowledge delivers comprehensive hands-on project management, business process, and professional skills training. Visit our online Knowledge Center at www.globalknowledge.com/business for free white papers, webinars, and more.