Constrained by the Triple Constraint

The biggest problem that I have with project management is that people keep telling you to manage the Triple Constraint. Typically when you are in a training seminar they do this with 3 pieces of string, one each for Time (schedule), Resources (cost), and scope. The problem is that if you only manage those variables, you are missing about half the project.

Defenders of the status quo will tell you that risk, quality and satisfaction are functions of schedule, cost and scope. And indeed they are, but people often don't consider risk, quality and satisfaction to be as important as as schedule, cost and scope. As a result, we have people who are good at using a Microsoft Project Plan to lay out a schedule, and assign people to the activities to generate a budget, but they lack the ability to account for quality and risk issues and rebound from satisfaction issues.

That super stinks. Instead of thinking about the triple constraint, think about the hexagonal constraint. BTW, I made this image.