Ignoring the article for a moment. I think one of the problems with agile-in-the-wild is that people who try to use it think in binary terms. In the original ma

Ignoring the article for a moment. I think one of the problems with agile-in-the-wild is that people who try to use it think in binary terms. In the original manifesto, the idea put forth pretty clearly is about rebalancing the way things are done -- not doing one thing instead of the other. For example, it's not "Working software instead of documentation" it's "Working software over comprehensive documentation". Agile should be a philosophy about development, not a set of rules. To make matters worse, Agile-as-a-product (with Seminars, and Books and whatever) seems to only amplify this. I've had scrum masters tell me very directly that "the proper agile procedure for such and such is..." or things very similar. It doesn't mean you don't have tools or process or contracts or whatever...and it's frustrating that most people don't seem to get that.