<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Design&gt;Project Management&gt;Planning</title>	<link>http://tc.eserver.org/dir/Design/Project-Management/Planning</link>
	<description>A listing of the most recently indexed works about Design and Project Management and Planning 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>Design&gt;Project Management&gt;Planning</title>
		<link>http://tc.eserver.org/dir/Design/Project-Management/Planning</link>
	</image>
	<item>
		<title>Twenty Signs You Don’t Want that Web Design Project</title>
		<link>http://tc.eserver.org/33342.html</link>
		<guid>http://tc.eserver.org/33342.html</guid>
		<description>Most clients are good clients, and some clients are great clients. But some jobs are just never going to work out well. Herewith, a few indicators that a project may be headed to the toilet.</description>
	</item>
	<item>
		<title>You Need a Five-Year Plan for Your Website</title>
		<link>http://tc.eserver.org/33279.html</link>
		<guid>http://tc.eserver.org/33279.html</guid>
		<description>Websites change the way an organization communicates with its staff, customers, investors and general public. A change in communication is a major shift for the organization. To effectively implement such a change will take time. You need a five-year plan for your website.</description>
	</item>
	<item>
		<title>Gantt to Glory: Evolving from Project Management to Successful Web Operations</title>
		<link>http://tc.eserver.org/31745.html</link>
		<guid>http://tc.eserver.org/31745.html</guid>
		<description>Is the sheer possession of a PMP intended to be the Holy Grail of successful web projects, known to fail at a startling rate, or simply a way to divorce oneself from whatever outcome may result from the web project?</description>
	</item>
	<item>
		<title>Measure Twice, Cut Once</title>
		<link>http://tc.eserver.org/29434.html</link>
		<guid>http://tc.eserver.org/29434.html</guid>
		<description>Acting without planning can be expensive, and because of the potential cost of poorly thought-out actions, we should not only plan, but plan twice.</description>
	</item>
	<item>
		<title>Always Have a Backup Plan</title>
		<link>http://tc.eserver.org/23993.html</link>
		<guid>http://tc.eserver.org/23993.html</guid>
		<description>By anticipating failures, and designing backup plans, you can minimize the impact of unexpected problems on the user.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Design/Project-Management/Planning.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>