<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Resources&gt;Documentation&gt;Agile</title>	<link>http://tc.eserver.org/dir/Resources/Documentation/Agile</link>
	<description>A listing of the most recently indexed works about Resources and Documentation and Agile in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-08 by the EServer. All rights reserved.</copyright>
	<managingEditor>tclib-editorial@eserver.org (TC Library Editorial Board)</managingEditor>
	<webMaster>webmaster@eserver.org (Geoffrey Sauer)</webMaster>
	<image>
		<url>http://tc.eserver.org/images/newlogo.gif</url>
		<title>Resources&gt;Documentation&gt;Agile</title>
		<link>http://tc.eserver.org/dir/Resources/Documentation/Agile</link>
	</image>
	<item>
		<title>Best Practices for Agile/Lean Documentation</title>
		<link>http://tc.eserver.org/30729.html</link>
		<guid>http://tc.eserver.org/30729.html</guid>
		<description>Documentation is an important part of agile software development projects, but unlike traditionalists who often see documentation as a risk reduction strategy, agilists typically see documentation as a strategy which increases overall project risk and therefore strive to be as efficient as possible when it comes to documentation. Agilists write documentation when that&apos;s the best way to achieve the relevant goals, but there often proves to be better ways to achieve those goals than writing static documentation.  This article summarizes common &quot;best practices&quot; which agilists have adopted with respect to documentation.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Resources/Documentation/Agile.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>