Sorry, but I find the thread both:
a) Off-topic
b) Misleading. Iterative sofware methods require iterative documentation 
methods, but by no means do they eliminate the parallel need for early draft 
user manuals. In fact, Steve McConnell (Code Complete) proposes early draft 
user guides as an agile replacement for requirements specs.

Ben

> Because the application itself is built in an iterative process, rather than 
> being carved in stone, reacting to feedback from the client, documentation 
> before the last minute is pointless.  The reason should be obvious; the 
> application being documented in the early stages bears little resemblance 
> to the application delivered. 



Ben HechterVancouver BCbhechter at yahoo.com

Reply via email to