“I will take issue that Agile methods are no different from a take-it-or-leave-it standpoint as opposed to traditional process-oriented methods.”
There are two general approaches to implementation of any methodology in software development. One says you should treat the chosen method as a bible and adjust your organization to work exactly like it’s written in the books. Another says: here’s the thing, you can take whatever you want and leave whatever you don’t want but remember every decision brings its consequences.
While almost no one would admit to choose the former approach it’s quite often. Ask people why they don’t like Prince-2.
“- It is sooo heavy and formal.
- Why don’t you cut unneeded things off then?
- Can I??? They haven’t told me that.“
Personally I’m on the other end of spectrum. I believe you can use take-it-or-leave-it approach with virtually every software development methodology. Unlike Robert I believe that process-oriented methods are no different here. Even there you can decide to change only several areas and leave the rest unchanged if it works well for you. You just need to know what you resign from and why.