But isn't the documentation thing in the Agile manifesto?
- Working software over comprehensive documentation
I mean, sure, the whole "less talk, more rock" seems good in principle, but it denies the Pareto Principle. Just because something "works" once doesn't mean it'll work in all cases. I suspect that such thinking is why every time some company rolls something out to the public the server unexpectedly bursts into flames.
But it worked in test.
And "responding to change over following a plan" is a great way to flail at the end of a project and miss things like, oh, I dunno, security concerns? If I had a dime for every time a manager thought that decent prototype = shippable product, I'd have at least $10.80.
Agile sounds great for a prototype, but from my experience it doesn't sound like it scales too well. Management that is more interested in the prototype is a dangerous thing.