See "Agile Documentation" - a paper by by ScottAmbler, Copyright 2001, at http://www.agilemodeling.com/essays/agileDocumentation.htm

http://ecx.images-amazon.com/images/I/41XKx1BjjgL._BO2,204,203,200_SH20_OU01_.jpg

''(A question of AppropriateTechnicalDocumentation, perhaps?)''
----

This is a Very Good Article. Scott makes the important point that the decision on how much to invest in documentation is a decision that the stakeholder should make. Letting the decision be make for you either by historical momentum or the dictates of a process can be suboptimal for a project. -- DaveSmith

----

Very nice article.

A thought I had while reading the "4. When Does a Model Become Permanent?" section:
	 :	To make a model permanent, clearly its value must exceed its cost. But more than that, its value for the cost must exceed the 'value per cost' of the top stories you're working on. In other words, to defer the production of software that creates business value to produce documentation instead, the "bang for the buck" of the documentation needs to be greater than that of the business functions that are deferred.

But also keep in mind that the value of documentation includes the cost savings that accrue to you during the time you have it. So documentation that helps you understand user requirements or more effectively develop the software will be more valuable if developed sooner (and its value goes down the longer you defer creating it).

----

"Agile Documentation" is also the title of a book by Andreas Rueping - see my review at http://cplusplus.anthonyw.cjb.net/agile_documentation_review.html -- AnthonyWilliams

ISBN 0470856173

	 :	''A Pattern Guide to Producing Lightweight Documents for Software Projects''

----
CategoryPaper, CategoryBook