The Iron Triangle of Project Management: Scope, Time and Cost
The iron triangle is the simplest useful model in project management: scope, time and cost are linked, so you cannot change one without affecting the others. This guide explains each side, where the model came from, how trade-offs really work, and how to use it with a worked example and a simple priority exercise. It also covers what the triangle leaves out.
The iron triangle in one minute
Every project has three linked constraints: scope (what you deliver), time (when) and cost (how much).
Think of them as the sides of a triangle. Pull one side out and the others have to move, or the project loses quality.
The model is also called the triple constraint or the project management triangle. The name “iron triangle” reflects how rigid the links are.
The three constraints
| Constraint | What it covers | How you measure it | Common levers |
|---|---|---|---|
| Scope | The deliverables, features and work the project must produce, plus what is excluded. | Requirements met, deliverables accepted. | Add, remove or defer features. Change the level of detail. |
| Time | The schedule: start, milestones and finish date. | Milestones hit, schedule variance. | Re-sequence tasks, add capacity, move the deadline. |
| Cost | The budget: labor, materials, tools and other spending. | Spend against budget, cost variance. | Add or cut resources, change suppliers, adjust scope. |
Each side needs a baseline. The baseline is the approved plan that real progress is measured against. Our guides to project management metrics and the PMBOK planning process group cover how to set and track one.
Where the idea comes from
The exact origin is unclear. The triangle has been used since at least the 1950s.
One often-cited early version comes from Martin Barnes. In 1969 he designed a course on contract control with a triangle whose corners were cost, time and quality. He later replaced quality with performance.
You will also see the three sides named differently:
- Scope, time, cost (the most common).
- Budget, deadline, features.
- “On time, on spec, on budget.”
The popular saying “good, fast, cheap: choose two” is a shorthand for the same idea. Its attribution to John Ruskin has no supporting evidence, so be careful repeating it.
The history and variations of the model are well summarized in a reference article.
How trade-offs work
The rule is simple: a change to one constraint puts pressure on at least one of the others.
| If this changes… | Then expect… |
|---|---|
| Scope grows | More time, more cost, or both. If neither moves, quality drops. |
| Scope shrinks | Less time or less cost, or room to add quality. |
| Deadline moves earlier | Cut scope, add resources (more cost), or accept more risk and lower quality. |
| Deadline moves later | More room for scope or quality, but overhead costs often rise. |
| Budget is cut | Cut scope, or take longer with fewer people. If neither moves, quality drops. |
| Budget is increased | Faster delivery, more scope or higher quality, within limits. |
One caution. The trade-offs are not always one-for-one. Adding people to a late project does not always speed it up, as the next sections explain.
Uncontrolled change to the scope side is the classic way projects break the triangle. See our guide to project scope creep.
A worked example
This is an illustration, not real project data. The numbers are simplified to show the logic.
A team is building a customer portal. Baseline: 12 features, 30 weeks, $300,000. The team costs $10,000 per week, and each feature takes about 2.5 weeks.
The sponsor now wants to launch 6 weeks earlier, in 24 weeks. What are the options?
| Option | Scope | Time | Cost | Main risk |
|---|---|---|---|---|
| Baseline | 12 features | 30 weeks | $300,000 | Misses the new target date. |
| A. Cut scope | 9 features (3 deferred) | About 23 weeks (9 × 2.5 = 22.5) | About $225,000 (22.5 × $10,000) | Fewer features at launch. |
| B. Add capacity | 12 features | 24 weeks | $300,000 in theory; about $330,000 with 10% overhead (our assumption) | Onboarding and coordination can eat the gains. |
| C. Hold all three | 12 features | 24 weeks | $300,000 | Quality drops. This is the option the triangle warns about. |
For option B, 30 weeks of work in 24 weeks needs 25 percent more capacity, so the weekly cost rises from $10,000 to $12,500. That is 24 × $12,500 = $300,000 in a perfect world.
In real projects, new people need time to get up to speed, so plan for a premium.
The value of the triangle is that it turns “can we go faster?” into a clear choice for the sponsor: less scope, more money, or lower quality.
Compressing the schedule
When time is the constraint that has to move, two standard techniques exist.
| Fast tracking | Crashing | |
|---|---|---|
| What it does | Runs tasks in parallel that were planned in sequence. | Adds resources, such as people or overtime, to shorten tasks. |
| Effect on scope | None. | None. |
| Effect on cost | Little direct cost. | Cost rises. |
| Main risk | Rework, errors and burnout, because tasks overlap. | Higher cost and coordination overhead. |
| Works when | The overlapping tasks are not strictly dependent. | The tasks on the critical path can actually be shortened with more help. |
Fast tracking is usually tried first because it needs no extra budget. The two can be combined.
Why adding people does not always help
In 1975, Fred Brooks wrote in The Mythical Man-Month that adding manpower to a late software project makes it later. He later called this an oversimplification, but the underlying point holds.
There are two main reasons:
- Ramp-up. New people need time to learn, and teaching them pulls experienced people away from the work.
- Communication. More people means more links between them. A team of n people has n×(n−1)/2 possible one-to-one channels.
| Team size | One-to-one channels |
|---|---|
| 3 | 3 |
| 5 | 10 |
| 10 | 45 |
| 15 | 105 |
Some work also cannot be divided. Nine people cannot produce a baby in one month. Brooks used that image to make the point.
Caveats apply. The effect depends on how many people you add, their skills, and how well the work divides. Strong modular design lowers the overhead.
Where quality fits
Quality is not a fourth side of the triangle. It is the result of how well you balance the three.
Squeeze all three sides at once and quality is what gives. That is why many practitioners picture it in the middle of the triangle, as in the diagram above.
Other frameworks widen the model. A PMI conference paper on the topic describes six constraints used by PRINCE2: cost, risk, benefits, quality, scope and time. Its main argument is that sponsors easily measure time and cost, while scope, quality, benefits and risk are often neglected.
The paper also makes the point that delivered scope is not the same as benefits.
The limits of the model
The triangle is a good starting point, not the whole picture. Critics point out that it:
- Leaves out outcomes. A project can hit scope, time and cost and still fail to deliver value, or leave users unhappy.
- Is vague about scope. The third side is sometimes called scope, quality, performance or deliverables, and these are not identical.
- Assumes trade-offs are always possible. Adding people can slow a project down, and in poorly run projects, improving one side can harm quality.
- Hides risk. Risk and uncertainty are not on the triangle at all.
Use it as a conversation tool with sponsors, and pair it with benefits, risk and stakeholder satisfaction. For what typically goes wrong, see why projects fail and the top 10 project management challenges.
The triangle in agile projects
Agile teams use the same idea in a different way. They commonly hold time and cost steady and let scope flex.
PMI’s PM Network describes this practice: groom the backlog each sprint, and when something new is added, swap it for something of similar effort so the timeline and budget stay fixed.
The triangle has not gone away. The team has simply chosen which side bends. For more context, read why agile project management is growing.
How to use it day to day
Run a priority exercise at kickoff
Ask the sponsor to rank the three sides. The goal is to find which one is fixed and which one can bend.
| Mark each side as… | Meaning | Example |
|---|---|---|
| Fixed | Must not move. | A regulatory launch date. |
| Flexible | Can move within agreed limits. | Budget can rise by up to 10%. |
| Open | The side that gives first when pressure comes. | Lower-priority features can slip to phase two. |
Only one side should be open, and not all three can be fixed. Write the answer into the project charter.
Then keep the triangle healthy
- Define scope clearly, including exclusions. See requirements management.
- Baseline all three sides and get sign-off.
- Track variance on each side regularly, not only at milestones.
- Route every change through change control. Price its effect on all three sides before saying yes.
- Show the trade-offs to the sponsor as options, as in the worked example.
- Revisit the triangle at each phase of the project lifecycle.
Frequently asked questions
What is the iron triangle in project management?
It is a model showing that scope, time and cost are linked. A change in one affects at least one of the others, and quality depends on how well the three are balanced.
Is the iron triangle the same as the triple constraint?
In everyday use, yes. “Iron triangle,” “triple constraint” and “project management triangle” all describe the same model.
What are the three sides of the iron triangle?
Scope, time and cost. Some versions use budget, deadline and features instead, or add quality in the middle.
Where does quality fit in the iron triangle?
Quality is usually treated as the result of balancing the three sides. If you squeeze scope, time and cost together, quality suffers.
What is the difference between fast tracking and crashing?
Fast tracking overlaps tasks that were planned in sequence. Crashing adds resources to shorten tasks. Fast tracking risks rework. Crashing raises cost.
Why does adding people to a late project not always help?
New people need time to ramp up, and more people means more communication links. Some work also cannot be split up. This is known as Brooks’s law.
Is the iron triangle still useful?
Yes, as a simple tool for explaining trade-offs. It works best alongside measures of risk, benefits and stakeholder satisfaction, since it does not cover them.
Compare project management certificate programs side by side.