<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Documentation&gt;Agile&gt;Workflow</title>	<link>http://tc.eserver.org/dir/Articles/Documentation/Agile/Workflow</link>
	<description>A listing of the most recently indexed works about Articles and Documentation and Agile and Workflow 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>Articles&gt;Documentation&gt;Agile&gt;Workflow</title>
		<link>http://tc.eserver.org/dir/Articles/Documentation/Agile/Workflow</link>
	</image>
	<item>
		<title>An Agile Review Process for Technical Documentation</title>
		<link>http://tc.eserver.org/31163.html</link>
		<guid>http://tc.eserver.org/31163.html</guid>
		<description>Documentation teams need a fast and effective review process to move forward on their projects and deliver quality, timely content. Reviewers, may they be SMEs (Subject Matter Experts) or key organization authorities, are usually extremely busy and have limited time (or interest) to review documentation. Interesting dilemma, no?</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Documentation/Agile/Workflow.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>