[copsarebastards]

Starting your post with "But" makes it seem like you're disagreeing with what I said.

"Agile as it is practiced" is not what I was talking about and has very little relation to the agile manifesto. The agile manifesto isn't a methodology, it's a philosophy. I would go so far as to say that "Agile process" and "Agile methodology" are oxymorons if you're using "agile" in the "agile manifesto" sense.

Everything you said in your post is a direct consequence of prioritizing individuals and interactions over processes and procedures: the first statement of the agile manifesto.

I realize I am being one of those "you're doing agile wrong" people, but only because I feel that it's worth rescuing "agile" from "Agile" because otherwise we're just rediscovering the same principles under a different name. I would rather fight to remove the pollution of "Agile methodologies" from the actual meaning of the agile manifesto than reinvent the wheel, and run into the same issues where people coopt the principles and pretend they support whatever flavor-of-the-week methodology they are espousing.