Website overview: Since 1996 the Study Guides and Strategies Website has been researched, authored, maintained and supported as an international, learner-centric, educational public service.
Permission is granted to freely copy, adapt, and distribute individual Study Guides in print format in non-commercial educational settings that benefit learners.
Please be aware that the Guides welcome, and are under, continuous review and revision.
For that reason, digitization and reproduction of all content on the Internet can only be with permission through a licensed agreement. Linking to the Guides is encouraged!
Agile documents are "lean and sufficient" . An agile document contains just enough information to fulfill its purpose, in other words it is as simple as it can possibly be. For example, portions of an agile document could be written in point form instead of prose-you're still capturing the critical information without investing time to make it look pretty, which is in accordance to the principle Content is More Important Than Representation . Agile documents will often provide references to other sources of information, for example a contract model describing the interface to an external system could indicate that the SOAP protocol is being used and provide a reference to the XML DTD and schema definition which define the XML documents transmitted between systems. When writing an agile document remember the principle Assume Simplicity , that the simplest documentation will be sufficient, and follow the practice Create Simple Content whenever possible.