Wednesday 2 July 2008

Agile documentation

Interesting post on BCS blog on agile management led me to the concept of TAGRI - They Aren't Gonna Read It: http://www.agilemodeling.com/essays/tagri.htm.

Some interesting thoughts of how documentation should be produced - working with the customer, to provide communication not documentation for documentation sake, writing to a good enough standard.
http://www.agilemodeling.com/essays/agileDocumentation.htm

Some of the questions posed could apply to anyone writing any kind of documentation. Interestingly, they don't advise using templates as each system is different so will require different documentation - the thinking is that the template is resource-intensive to create; the template will ask for detail which isn't always relevant but people will attempt to write something; thus reviews take longer because there's so much more information to read through.