<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Collaboration&gt;Project Management&gt;Technical Writing</title>	<link>http://tc.eserver.org/dir/Articles/Collaboration/Project-Management/Technical-Writing</link>
	<description>A listing of the most recently indexed works about Articles and Collaboration and Project Management and Technical Writing in the field of technical communication (and technical writing).</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;Collaboration&gt;Project Management&gt;Technical Writing</title>
		<link>http://tc.eserver.org/dir/Articles/Collaboration/Project-Management/Technical-Writing</link>
	</image>
	<item>
		<title>How Soon is Now?</title>
		<link>http://tc.eserver.org/35586.html</link>
		<guid>http://tc.eserver.org/35586.html</guid>
		<description>One common complaint a lot of technical writers have is that they aren’t included early enough in lifecycle of a project. The downsides are that by the time work hits your desk you don’t have a full picture of who the customer is, why they want whatever it is you are building, and how they want it provided to them. All of which directly impacts the information being created.</description>
	</item>
	<item>
		<title>When Trust Becomes a Characteristic Flaw in a Project</title>
		<link>http://tc.eserver.org/33551.html</link>
		<guid>http://tc.eserver.org/33551.html</guid>
		<description>As hard as it may seem, lesson one of technical writing is to break the rules and contact the end user. Conduct a mini-ethnography. Sit with the users. Call them on the phone. Send them emails. Do not let it get to the point where you feel you must go through the PM to communicate with the end user. As hard and uncomfortable as it may be, the consequences of not talking to the end user can be crippling to your help.</description>
	</item>
	<item>
		<title>The Hidden Relationship Between Project Managers and Technical Writers</title>
		<link>http://tc.eserver.org/29336.html</link>
		<guid>http://tc.eserver.org/29336.html</guid>
		<description>Want to know the secret to better quality documentation and improved software design? Will Kelly outlines how the key is an effective relationship between project managers and technical writers.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Collaboration/Project-Management/Technical-Writing.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>