You can't hold scope, time, and cost fixed at the same time. We look at project management's classic 'iron triangle' and the difference between agile and waterfall.
One of the oldest and most durable concepts in project management is the "iron triangle": scope, time, and cost. These three variables are so tightly linked that holding one fixed while keeping the other two fixed too is nearly impossible — when one changes, at least one of the others has to change with it.
When a client says "let's add scope but keep the deadline and budget the same," you're facing project management's core truth: you can hold two of these three variables fixed, but the third becomes a dependent outcome. If scope grows while time and budget stay fixed, quality — the invisible fourth variable — is what quietly takes the hit. A good project manager's job isn't to hide that trade-off, but to make it visible upfront.
The waterfall approach works well for projects where requirements are clear and stable from the start: scope is fully defined first, then design, development, testing, and delivery follow in sequence. Agile is designed for projects with high uncertainty, where requirements become clearer as work progresses: work is broken into small cycles (sprints), feedback is gathered at the end of each cycle, and scope is adapted accordingly. The right approach depends on the level of uncertainty, not the type of project.
The PMBOK (Project Management Body of Knowledge) guide published by the Project Management Institute (PMI) is one of the most widely recognized project management standards in the world. Its real value is providing a shared language so project managers across industries use terms like "scope," "stakeholder," and "risk" with the same meaning.
The first question to ask before starting your next project isn't which methodology to use — it's which variable (scope, time, or cost) genuinely isn't flexible for you.
Explore more of our articles on this topic.
