<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Project Management&gt;Planning</title>	<link>http://tc.eserver.org/dir/Articles/Project-Management/Planning</link>
	<description>A listing of the most recently indexed works about Articles 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>Articles&gt;Project Management&gt;Planning</title>
		<link>http://tc.eserver.org/dir/Articles/Project-Management/Planning</link>
	</image>
	<item>
		<title>Lying in a Hammock, or, Having a Single Goal without a Purpose</title>
		<link>http://tc.eserver.org/34890.html</link>
		<guid>http://tc.eserver.org/34890.html</guid>
		<description>When you live in the moment, completing the activity itself is the success. And because writing is so multifaceted in effect — the effect both on me and others — having an open purpose doesn’t limit the results. I’m not narrow-mindedly searching for a specific achievement to happen. Instead, I’m open to unconsidered possibilities, if any of those possibilities decide to unravel.</description>
	</item>
	<item>
		<title>Create Effective Project Milestone Sheets</title>
		<link>http://tc.eserver.org/34772.html</link>
		<guid>http://tc.eserver.org/34772.html</guid>
		<description>The project milestone sheet is an incredibly important document for freelancers and their clients. It defines all the most important tasks, who is assigned to them, and when they are due. In other words, it serves as the map for your entire work process.</description>
	</item>
	<item>
		<title>Reusing the User Experience</title>
		<link>http://tc.eserver.org/34645.html</link>
		<guid>http://tc.eserver.org/34645.html</guid>
		<description>As a rule of thumb, the earlier in the development process reuse can occur, the more efficient reuse becomes. Like software component reuse, the reuse of UX design elements can be a very efficient form of reuse—particularly because this form of reuse occurs very early in the product development cycle. The ability to reuse prior work effectively is one characteristic of a mature discipline.</description>
	</item>
	<item>
		<title>Successful Project Management: Using Time Management Tools</title>
		<link>http://tc.eserver.org/34094.html</link>
		<guid>http://tc.eserver.org/34094.html</guid>
		<description>In this introductory column, I’ll discuss time management and some ways in which you can use quick-reference sheets and project-management tools to help you maintain some semblance of sanity in your busy life.</description>
	</item>
	<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>Requirements Planning: Overlooked and Undervalued</title>
		<link>http://tc.eserver.org/32244.html</link>
		<guid>http://tc.eserver.org/32244.html</guid>
		<description>This article takes a high-level look at project requirements and the requirements cycle to help you understand the role of the business analyst in requirements planning.</description>
	</item>
	<item>
		<title>Be Productive When a Project Stalls</title>
		<link>http://tc.eserver.org/31849.html</link>
		<guid>http://tc.eserver.org/31849.html</guid>
		<description>With more and more companies adopting the Darwin Information Typing Architecture, Baril discusses how to choose a compatible content management system that also supports your company&apos;s processes. </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>Everything in Moderation: Using Content Units to Manage UX</title>
		<link>http://tc.eserver.org/31598.html</link>
		<guid>http://tc.eserver.org/31598.html</guid>
		<description>I’ve found that separating client requests into content units removes uncertainty and offers clearer direction, while helping your client recognize each individual request as a deliverable, requiring assignments and responsibilities. To do this, I follow a four-step process that helps delineate what content units each section of a Web site must cover—as opposed to content that acts as filler, or filler units.</description>
	</item>
	<item>
		<title>Fixed Quotes and Broken Promises</title>
		<link>http://tc.eserver.org/30353.html</link>
		<guid>http://tc.eserver.org/30353.html</guid>
		<description>How to tie down the details of a project and protect yourself from unexpected changes that can drag a &apos;peach project&apos; into the &apos;pits of despair and financial ruin.&apos;</description>
	</item>
	<item>
		<title>How to Plan On-line and Paper Versions of a Software Manual</title>
		<link>http://tc.eserver.org/30314.html</link>
		<guid>http://tc.eserver.org/30314.html</guid>
		<description>On projects for which you must produce both on-line and paper documentation, there are many things you should consider before you start.</description>
	</item>
	<item>
		<title>The Six Biggest Mistakes Project Managers Make with Documentation and How to Avoid Them</title>
		<link>http://tc.eserver.org/30262.html</link>
		<guid>http://tc.eserver.org/30262.html</guid>
		<description>Professional business writers, such as technical authors, typically break a document down into small, discrete units of information, organised around a skeleton of topic headings. If you use this &apos;component&apos; or &apos;modular&apos; approach, you can plan and structure the document using the heading &apos;labels&apos; that describe each section.</description>
	</item>
	<item>
		<title>Playing to Win: Building a Strategic Plan</title>
		<link>http://tc.eserver.org/30240.html</link>
		<guid>http://tc.eserver.org/30240.html</guid>
		<description>This workshop uses games to provide an overview of strategic planning. The first step in strategic planning is identifying the objectives of your project. Participants play a version of musical chairs to identify and prioritize objectives. The second step is developing a vision of meeting those objectives. Participants play a version of darts. The third step is building the plan that fulfills the vision. Participants play a board game to create the best plan with limited resources.</description>
	</item>
	<item>
		<title>High-Cost Usability Sometimes Makes Sense</title>
		<link>http://tc.eserver.org/30195.html</link>
		<guid>http://tc.eserver.org/30195.html</guid>
		<description>Computing the net present value (NPV) lets you estimate the most profitable level of usability investment. For big projects, expensive usability can pay off.</description>
	</item>
	<item>
		<title>Usability Requirements: Making User Satisfaction a Measure of Product Success</title>
		<link>http://tc.eserver.org/29905.html</link>
		<guid>http://tc.eserver.org/29905.html</guid>
		<description>Defining usability requirements at the beginning of the project increases the chances that the end product will meet the users&apos; goals and create a satisfying user experience. Unfortunately, such requirements are often not considered with the same priority as functional or other technical requirements. This presentation defines usability requirements, proposes guidelines for creating measurable requirements, and elaborates the components of a well-constructed usability requirement.</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>Document Planning Checklist</title>
		<link>http://tc.eserver.org/21681.html</link>
		<guid>http://tc.eserver.org/21681.html</guid>
		<description>You need to anticipate the lifecycle of technical publications in advance so that all areas related to the final delivery are covered. These include issues such as costs, production, dissemination and archiving.</description>
	</item>
	<item>
		<title>Flowcharting Performance-Based Processes and Procedures</title>
		<link>http://tc.eserver.org/20066.html</link>
		<guid>http://tc.eserver.org/20066.html</guid>
		<description>This session distinguishes between analytical- and performance-based flowcharting of process and procedures. The session will present why, how, and when&#xD;flowcharting is considered superior to text alone, along&#xD;with defining flowcharts and symbols. The session&#xD;distinguishes between processes and procedures and the&#xD;various styles, formats, and trends that have developed&#xD;historically primarily due to different origins, purposes,&#xD;and technologies. The session also presents&#xD;recommended standards for creating flowcharts, and&#xD;addresses issues on tools, training, and trends.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Project-Management/Planning.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>