Agile or Waterfall - considering scope changes

I received this interesting question on Project Management methodologies:

Question:
"Is Agile better suited than Waterfall for handling continuous scope changes?"

My answer:
Probably yes, Agile is more adapted to change than a classical Waterfall approach. The addition of new features and changes is the essence of the Agile approach: get a prototype as soon as possible and make the product better and better as the needs arise.

One of the arguments against Waterfall is precisely this, although it is not true at all that a waterfall environment in a project would not allow for changes. Have you ever seen a project that had no changes at all during the project cycle? Scope change is also a very important part of any Waterfall approach.

The correct answer for your project will probably be dependent on factors like industry, company culture, type of final deliverable, etc...