Agile life in a ISO9001 world

It seems that all you have to do these days is name drop in certain situations to add masses of validity to your situation. This is no less true in Project Management, dropping the heavy "prince2" name in a specific circumstance can turn heads. It now seems that the same can be said for Agile software development but it has an impact that many companies may overlook. Jumping on the Agile band wagon is certain to increase productivity and success of a software engineering project as both Boehm and Glass would agree but very few companies realise the impact of repeatability and recording of the projects under this methodology which will effect any ISO or CMM processes in place.

Yes we want a process which allows for flexability of client requirements and yes we also want a methodology which has been proven to increace project success, but do we want this at the risk of reducing the quality of the proccess? But if the project IS different then IS the process different?

In my opionion the Agile methodologies do allow you to maintain your repeatable, recordable proccess but how can you avoid the state mindless beurocracy? Is would suggest that maybe it is time for the powers of ISO and CMM certification bodies to take a stand and keep up-to-date with how software engineering is progressing and allow this progresseion to speed up without exxesive 'certification' inertia.