Project constraints: Using the wrong terminology?
We're all familiar with the triple project constraints of time, cost and scope and there's been plenty of debate about whether other constraints should be factored in to the constraint triangle but I'd like to take a step backwards and consider whether "constraint" really is the right description and whether we, as a profession, could better describe how a project is actually constrained and what we really mean by the "triple constraints".