The Triple Constraint is a paradigm that is applicable to any kind of project. It is used to illustrate how changes in competing demands are inter-connected, and how changing one has an effect on the others.
The Basics
As a straightforward way to talk about various limits and demands of a project, the Triple Constraint is useful in talking about a project's end result. One way to talk about this is in the old adage posted on the walls of plumbing and electrical shops, "You can have it quick, cheap, or good. Pick any two". In today's lingo, this has been translated into the three-point triangle of the Triple Constraint:
The idea remains the same: although the limits of an overall result may be flexible, unless a project manager is able to work some kind of magic, a change in one of these elements will produce a change in another.
You Get What You Pay For
Regarding the Cost principle: this point of the Triple Constraint can be boiled down into just that: the cheaper your cost, the less quality you will get. For example, when labor is rushed to make up for a lower project budget, or when a project can be completed more quickly for a higher cost, we call Time vs. Cost. Other changes in cost effect the project's scope in various ways. Factors in Cost include materials, labor rates (which can change based on the time principle), and other aspects like risk management. Project managers try their best to identify cost components and communicate them to the client to get better result. Some called "client education": it helps streamline the understanding of what the result will be, and helps avoid critical problems in a project's 'endgame', when a client might have complaints about cost factors that weren't made clear earlier.
A Scope Example: Project Inflation
Scope is a critical factor in a project that always effects other variables. The less a contractor has to do, the quicker it can be done, and the lower the cost will be. This is pretty straightforward, but many times, Scope problems (some caused, again, by insufficient communications) threaten to make a project collapse. Project Inflation happens when a client wants to increase the scope of a project without changing the cost or time. Imagine the individual workers in a company providing a service, for example, widgets. The client calls and asks for many more features on the widgets, without expanding the project budget or providing more time. This throws the provider into a tailspin as managers struggle to "make it fit". Here is where communicating the Triple Constraint can really save everyone a lot of headaches. In some cases, the client is really unaware of the problems they are causing, but in other cases, the client may be deliberately squeezing a service provider to test their limits and trying to push against the inevitable Triple Constraint principle. In either case, someone should let the client know that Scope can be changed only with resulting changes to Time and/or Cost.
Putting the Triple Constraint in Your Toolbox
There are many scenarios where project managers will encounter the Triple Constraint, keeping this principle in mind will help a manager:
- know when to approach the subject
- what to say about it when balancing between a client's demand
- what is feasible in-house
That's why the time-tested truism is popular with managers everywhere!