Thanks for the heads up. Since posting the article I've had a few other people issue similar words of caution.
What I do like about this article is that it does highlight several valid criticisms of agile - that it's very mechanical and focused on short-term goals, but agile also has it's merits (a focus on rapid iteration rather than BDUF, good code hygiene and refactoring and collaborative coding).
What I really would like to see in an article is a comparison to other development methodologies which covers where and when they're appropriate. I suspect that if you talk to the original proponents of agile, they'll suggest it's a little more subtle than a one-size-fits-all process for all teams and projects. Much like selecting a development tool, you want to some thought put into whether this the right process for your