I was working on figuring out the latest Visual Studio Database Edition GDR when I came across this Microsoft definition of Agile Methods:
A family of processes that application developers use to minimize risk by developing applications in a series of short iterations that last one to four weeks. In this paradigm, the primary measure of progress is working software, instead of hours spent or tasks completed. Agile Methods emphasizes real-time communication, such as face-to-face meetings, telephone calls, and instant messaging, over written documents.
The documentation asked for Feedback. Who am I to shrink from that?
Here is an except of the Wikipedia entry for Agile Software Development that is closer to the real meaning:
Agile methodologies generally promote a project management process that encourages frequent inspection and adaptation, a leadership philosophy that encourages teamwork, self-organization and accountability, a set of engineering best practices that allow for rapid delivery of high-quality software, and a business approach that aligns development with customer needs and company goals.
Notice that there is a reference to a "set of engineering best practices" (one of which — developer-level unit testing — is supported directly by the Database Edition, yet no mention).
Notice also that there is no mention of a dearth of documentation. Documentation is a requirement to be prioritized along with the working software aspect. But I digress.
My primary concern is that it be clear that Agile Methods stress a disciplined approach to creating high-quality software through engineering best practices. It is not chaos with no documentation as generally assumed by those who don’t know any better.
And I’ll keep pointing that out whenever it’s necessary…