By Décio Dalke Jr. · Nov 2026

The holy trinity of project management: scope, time, resources

Scope, time and resources make up a project's triple constraint. Why anyone who fixes all three at once has already chosen, without knowing it, where the project will give way.

New to this topic? Start with World 1 of Projects.

Move one, move all three — pixel-art triangle of three bars with a dot in the middle and one side bent

Décio Dalke Jr. — Arquiteto de negócios. Sócio-gerente no ecossistema MitUP (mitup.pt).

Every project rests on three things that pull on one another: what will be delivered, by when, and with how much. Scope, time and resources. In the project management literature this has a name, the triple constraint, and it is usually drawn as a triangle with quality in the middle [1].

What is the triple constraint?

It is the idea that scope, time and resources are tied together. The drawing is attributed to Martin Barnes, who used it in a course on time and cost control in 1969 [1][2]. Since then it has picked up variations, with risk, benefit and other corners, although the core has stayed the same.

Whoever increases the scope needs more time, more resources, or both. Whoever cuts the time needs more resources or less scope. Whoever cuts resources stretches the time or shrinks the delivery. None of the three moves on its own.

Why call it a holy trinity?

Because there are three of them, and in practice they work as one. In level 2 of World 1 of Projects the scope became a WBS; in level 3, the WBS became schedule, resources and cost, linked together. The trinity is that same chain seen from above: pull any link and the other two come with it.

Where does it break?

Almost always in the same place: when someone fixes all three corners at once. Fixed scope, fixed date, fixed budget, and no slack declared anywhere. The triangle doesn’t close, and the difference usually comes out of the variable that suffers most at those moments: quality. Or a knock-on effect on people and resources and, in the end, on the project’s time and deadline. Which invariably brings costs and losses. That is what makes the maths beautiful: the sum has to add up and there is no such thing as a free lunch. If we have three variables and we always find the third by working it out from the first two, there is no magic that lets you hammer all three at once and keep everything else unchanged. Somebody always pays the bill!

Some years ago I was on an industrial project where the client wanted to cut six months off the final deadline because they had “contracted it wrong”. They needed to open the project earlier so that it coincided with other projects on the site. But they didn’t want to pay for acceleration. In other words, more people in less time but at the same cost. You don’t need to be an expert to know that it didn’t go well. The deadline wasn’t brought forward. And the cost to them was higher than the acceleration they hadn’t wanted to pay for.

Who decides which corner gives way?

Whoever owns the project, and preferably before it starts. Asking right at the beginning which of the three can move, if something goes wrong, is one of the cheapest conversations a project can have. Held in the middle of a crisis, the same conversation costs a great deal more, and almost always the one deciding is the calendar or the wallet.

Quick questions

What is the triple constraint? The relationship between scope, time and resources in a project: changing one forces you to adjust at least one of the other two.

Is quality part of the triangle? In many versions it sits in the centre, as the result of the balance between the three corners. When all three are fixed, it is usually quality that gives way.

Can you fix scope, time and resources at the same time? Only with slack declared somewhere. Without slack, one of the three will give way, and most likely it will give way without anyone having decided.

References

[1] Wikipedia — Project management triangle: https://en.wikipedia.org/wiki/Project_management_triangle (accessed 29/10/2026) [2] Devopedia — Iron Triangle: https://devopedia.org/iron-triangle (accessed 29/10/2026)