The triple constraint of project management describes the interdependency between the three cornerstones of a project:
Applying common sense, it seems obvious that changing one of the three cornerstones implies a change of the other two.
For example, if we increase the scope - because of additionally
required features of the product – then we obviously have to increase
the necessary time and amount of money. Similarly, in order to shorten
the time we could reduce the scope and consequently reduce the budget of
that project. We also could shorten the time by involving more
resources and thus, increasing the budget.
In short, we can say:
A project is defined by its scope, schedule, and budget, and the triple constraint of project management describes the phenomenon that, if we change one of the three, we influence the other two.
Looking at it a little bit closer, we find that constraints of project management are mainly limited resources.
The triple constraint of project management is rooted in the theory of constraints (TOC), first formulated by Dr. Eliyahu M. Goldratt in his book The Goal, published in 1984.
We can measure and control an organization by varying three basic variables: throughput, operating expense, and inventory. Throughput is the money all sales activities generate (simplified: income). Operating expense is money we need in order to ensure the organization's operation on an ongoing basis (simplified: recurring cost). Inventory is money we invest in order to produce and sell goods and services (simplified: non-recurring cost).
Underlying assumption of the theory of constraints is that an organization is limited in achieving its goals by a small number of constraints, and that there is always at least one constraint. A constraint can be internal or external to the organization.
As with the triple constraint of project management, an organization should try to find its constraint(s), and then improve managing them in order to better achieve its goals. More precisely, the theory of constraints suggests:
Step 1. Identify the constraint (those resources or policies that prevent the organization from achieving its goals).
Step 2. Decide how to utilize or change the constraint and its elements to the advantage of the organization.
Step 3. Make sure that all other processes comply with this decision.
Step 4. Raise the constraint (e.g. increase the capacity of the constraint).
Step 5. If, as a result of these steps, the constraint has moved, return to Step 1.
One application of the theory of constraints is critical chain project management.
In case you would like to use practical and useful packages of tools, templates and checklists, here you can get them. They save you a lot of time, are easy to use and easy to change:
All four PM Phases in one Set