Originally posted on: http://geekswithblogs.net/MSARCH/archive/2016/04/07/174112.aspx
I found this on Udi Dahan's blog on an tangentially related topic:
"The thing is that Agile Manifesto never said to intentionally bury your head in the sand with regards to the purpose of the system. It was a push-back against spending months in analysis without anything but documents coming out, but the goal was to reach a middle ground. Nobody ever said 'no design up-front” or “no requirements up front'." (http://udidahan.com/2012/03/29/a-cqrs-journey-with-and-without-microsoft/)
I think this derives from the Manifesto principle: Responding to change - over following a plan. To that I agree with Udi that this agile principle does not say "Don't have a plan", but rather says "Allow your plan to be flexible." Sometimes agile abandons good principles for a rigid process.
