In fact the words "Agile", "XP" and "SCRUM" have pretty much turned into red flags for me. My immediate reflex whenever someone feels a need to mention those to me is to bill by the hour - because anything else would probably come back and haunt me iteratively ...
Even in true management fads, there's usually a grain of truth in there somewhere.
Just don't be the guy who never picks up any new skills because 1) people usually misapply them, or 2) you had a bad experience. Everything is a tool in your toolbox. Lots of tools means lots of options.
I've found that even with "heavy" process overhead, like CMM or CMMI, if you talk to the developers they're supposed to be practical and make sense. It's the way people in companies apply these things that are usually at the heart of why they don't work. At the end of the day, it all gets back to people.
I tell my PMs that I train that no, I do not want them to be the CSM. I want them to work strategically, to work on all of those organizational obstacles that get in the team's way. You can't change the world, but good agile teams are going to be constantly reminding the CTO and everybody else that certain constraints are killing team performance.
You can treat it like a fad if you want -- just throw new labels on old crap. But whether it's Scrum, Agile, or Bob's New Process, at the end of the day the teams must communicate back to the organization frequently about what's screwed up. And the organization must listen. Or you can just keep throwing money and fads at problems you won't acknowledge. Reality is reality. The reason you end up with poor understanding at the CTO level is because nobody has the balls to tell him what's really going on. That conversation is the toughest part of adapting in a nutshell (pun not intended).