It's all about trade-offs. Yeah, a semi-big project involving more than four or five developers needs some sort of organization process for how to report progress and document what needs to be done and who's responsible.

But you're spot-on when the activities of talking and documenting getting things done eclipse actually getting things done. Every methodology, programming language and framework always gets its ardent followers, and some of them take it to extremes that "The Foo project engineering/ Bar language/ Baz on Rails will heal all." But it's bullshit. Most of these things are very useful tools, and we may have personal preferences, none of them are a silver bullet. But some people you give a hammer to, every problem looks like a nail. And to toss away an otherwise good candidate who is a bright self-starter because they don't know $PREFERRED_DEVELOPMENT_METHODOLOGY_DU_JOUR is just frankly fucking stupid. If it's so damned important, give 'em a book on it and toss them in. They'll figure it out. And if they can't, that's not someone you want anyway.