<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Presentations&gt;Management&gt;Documentation</title>	<link>http://tc.eserver.org/dir/Presentations/Management/Documentation</link>
	<description>A listing of the most recently indexed works about Presentations and Management and Documentation 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>Presentations&gt;Management&gt;Documentation</title>
		<link>http://tc.eserver.org/dir/Presentations/Management/Documentation</link>
	</image>
	<item>
		<title>Managing a Documentation Project: A Guide</title>
		<link>http://tc.eserver.org/35436.html</link>
		<guid>http://tc.eserver.org/35436.html</guid>
		<description>This a short video overview of managing a documentation project. It&apos;s something we put together as a test of some of the functionality of Techsmith&apos;s Camtasia software.</description>
	</item>
	<item>
		<title>Analyzing Your Deliverables: Developing the Optimal Documentation Library</title>
		<link>http://tc.eserver.org/35338.html</link>
		<guid>http://tc.eserver.org/35338.html</guid>
		<description>Web 2.0 includes: wikis, podcasts, blogs, widgets/gadgets, social networks … and combinations of all the above. Not everyone contributes equally – Creators (18%), Critics (25%), Spectators (48%). But all are important.</description>
	</item>
	<item>
		<title>Project Management and the Technical Communicator</title>
		<link>http://tc.eserver.org/29526.html</link>
		<guid>http://tc.eserver.org/29526.html</guid>
		<description>Describes how project management can help technical communication professionals better plan and manage their technical documentation projects.</description>
	</item>
	<item>
		<title>Wikis Are Coming: An In-Depth Exploration of Using Wikis in Documentation</title>
		<link>http://tc.eserver.org/28754.html</link>
		<guid>http://tc.eserver.org/28754.html</guid>
		<description>In this podcast, Katriel Reichman, a technical writer at Method M in Jerusalem, Israel, talks in-depth about how to use wikis for documentation.</description>
	</item>
	<item>
		<title>Modelling Information, or Documentation Planning for Dummies</title>
		<link>http://tc.eserver.org/23167.html</link>
		<guid>http://tc.eserver.org/23167.html</guid>
		<description>Identify the user. Identify the user&apos;s goals. Drill down to task level. Establish what the user knows. Identify what the user needs to know. Identify what the user should NOT know.</description>
	</item>
	<item>
		<title>Decision Making: A Missing Facet of Effective Documentation</title>
		<link>http://tc.eserver.org/13942.html</link>
		<guid>http://tc.eserver.org/13942.html</guid>
		<description>The old school of software interface design and document writing took the view that if the user could find the information someplace, the user could use it. But simply sticking in details ignores how readers access and process information.</description>
	</item>
	<item>
		<title>Using Databases to Manage Online Documentation</title>
		<link>http://tc.eserver.org/13683.html</link>
		<guid>http://tc.eserver.org/13683.html</guid>
		<description>Our methodology for knowledge base authoring guides you&#xD;through step-by-step examples of how to create and&#xD;maintain knowledge bases in a database. The methodology&#xD;allows your team to develop simple solutions for&#xD;information requests as well as sophisticated diagnostic&#xD;trees for troubleshooting. With the information stored in a database, you are able to easily access the information and use it for a variety of projects.</description>
	</item>
	<item>
		<title>Walking Through the Fires: A Case Study of Implementing a Formal Documentation Development Process</title>
		<link>http://tc.eserver.org/13682.html</link>
		<guid>http://tc.eserver.org/13682.html</guid>
		<description>The need for a more comprehensive documentation development process at Computerized Medical Systems, Inc. (CMS) was identified in an annual year-end review meeting of the CMS User Documentation Section. The goal was set to develop and implement such a process. A key component would be a set of comprehensive Content Specification Guidelines. Initial research consisted of reviewing existing literature and compiling a list of information considered essential to effectively plan a documentation project at CMS, based on discussion with software developers and technical communicators as well as experience gained from previous projects. The new process was implemented and has provided benefits throughout the company.</description>
	</item>
	<item>
		<title>Starting and Maintaining A Documentation Department: Concepts, Principles and Techniques</title>
		<link>http://tc.eserver.org/13215.html</link>
		<guid>http://tc.eserver.org/13215.html</guid>
		<description>Starting and Maintaining a Documentation&#xD;Department – Concepts, Principles and Techniques”&#xD;includes information about assessing business needs,&#xD;establishing credibility, building the department,&#xD;understanding the product life cycle and development&#xD;practices, and successfully maintaining a&#xD;documentation department. It includes innovative,&#xD;creative, and original management concepts, tasks, principles, techniques for newly promoted managers, managers new to a company, and for seasoned managers to ensure success or continued success managing documentation departments.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Presentations/Management/Documentation.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>