Iron Triangle
The project management model stating that scope, time, and cost are interdependent constraints: you cannot change one without affecting the others or quality.
Also known as: Project Management Triangle, Triple Constraint, Good Fast Cheap, Pick Two, Iron Triangle of Project Management
Category: Frameworks
Tags: project-management, trade-offs, planning, constraints, mental-models
Explanation
The Iron Triangle, also called the project management triangle or triple constraint, is a model attributed to Martin Barnes (1969). It describes three constraints every project operates under: scope (what gets delivered), time (when), and cost (with what resources). Quality is often placed in the middle of the triangle because it is what absorbs the pressure when the constraints are not balanced.
## The Core Idea
The three sides are linked. If you add scope, you need more time or more money. If you cut the deadline, you need to reduce scope or add resources. If you cut the budget, something else gives. Trying to fix all three at once while demanding more of one of them does not make the trade-off disappear: it silently pushes it into quality, through bugs, technical debt, burnout, or shortcuts.
The popular shorthand is 'good, fast, cheap: pick two'.
## Using It Well
- **Make the trade-off explicit**: Ask which constraint is fixed and which one is allowed to move. Having all three fixed is a red flag.
- **Prefer fixing time and flexing scope**: Many modern methods (Shape Up, timeboxed sprints, MVPs) fix time and cost and treat scope as the variable. This keeps delivery predictable and forces prioritization.
- **Beware adding people**: Adding resources rarely shortens time linearly. Brooks's Law notes that adding people to a late software project makes it later.
- **Protect quality deliberately**: If quality is the hidden fourth side, state the quality bar explicitly so that it doesn't become the default sacrifice.
## Criticism
The model is a simplification. It ignores value, risk, and benefits, and success on all three sides does not guarantee that the project delivered anything useful. Later variants add risk, quality, and benefits as further dimensions. It remains useful as a quick reminder that wishes are not plans.
Related Concepts
← Back to all concepts