Collaboration and Documentation

by Jim Highsmith

The Agile Manifesto principle of "working software over comprehensive documentation" has often been misunderstood as either "no documentation" or an excuse for "ad hoc" development. In the principle statement, the word "over" implies that working software is more important than documentation, but not that the documentation isn't important or useful. Second, the word "comprehensive" denotes "heavyweight" rather than lean documentation. Maybe, rather than linking working software and documentation in a principle, the Manifesto might better have stated, "intensive collaboration over comprehensive documentation," because the emphasis in agile development is on collaboration first and documentation second -- or maybe even third or fourth.

Password Protected Cutter Consortium clients, please log in:


This document is available to Cutter Consortium Resource Center clients only. Retrieve password.
If you would like further information about how to become a client, please contact us at +1 781 648 8700 or sales@cutter.com.
Collaboration and DocumentationThu Sep 27 08:12:42 CDT 2007