That's fine but the first iterations were because they fucked the requirements up. Regardless of Agile/not, due diligence when selecting products or deciding to write them is required.
That notwithstanding, I'd also be very interested to know how agile is a panacea to fast-changing requirements, especially as opposed to techniques such as designing for change (at the architectural level, so not just the implementation level, i.e. loose coupling, encapsulation and abstraction interfaces).