<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Articles&gt;Management&gt;Quality</title>	<link>http://tc.eserver.org/dir/Articles/Management/Quality</link>
	<description>A listing of the most recently indexed works about Articles and Management and Quality in the field of technical communication.</description>
	<language>en-us</language>
	<copyright>Copyright (c) 2005-10 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;Management&gt;Quality</title>
		<link>http://tc.eserver.org/dir/Articles/Management/Quality</link>
	</image>
	<item>
		<title>Six (Sigma) Reasons to Embrace Enterprise Content Management</title>
		<link>http://tc.eserver.org/36425.html</link>
		<guid>http://tc.eserver.org/36425.html</guid>
		<description>Six Sigma is the formal discipline used to rethink and, if necessary, redesign business operations from a customer-centric position to improve business performance and maximize customer satisfaction. Customer-centric Enterprise Content Management (ECM) is all about customer-facing content, regardless of how the content reaches the customer, be it in print, on the Web, via interactive customer support systems, or over the telephone, where &quot;customer&quot; designates both internal and external recipients of content. The commonality between the two fields of practice is, of course, the customer. Often, however, the perception of Content Management is limited in the corporate consciousness to &quot;managing Web content.&quot; Six Sigma provides us with plenty of reasons to seriously consider ECM from a much broader perspective. ECM is no longer primarily a tool to manage Web content or technical documentation, but a key business strategy to enhance and improve the customer experience. This article explores six reasons to implement ECM as a strategic business initiative.</description>
	</item>
	<item>
		<title>Toward Content Quality</title>
		<link>http://tc.eserver.org/34233.html</link>
		<guid>http://tc.eserver.org/34233.html</guid>
		<description>How do we know whether content is any good? This simple question does not have a simple answer. Yet, I think having a good answer would help us show our employers and clients why their content needs to improve and how their content compares to the competition’s.</description>
	</item>
	<item>
		<title>Project and Quality Management for Beginners</title>
		<link>http://tc.eserver.org/30545.html</link>
		<guid>http://tc.eserver.org/30545.html</guid>
		<description>This discussion is intended for people who have recently assumed project management responsibilities (or want to). Project and quality management is about developing a plan, working the plan, and evaluating the results.</description>
	</item>
	<item>
		<title>Controlling Quality, Controlling Costs</title>
		<link>http://tc.eserver.org/30417.html</link>
		<guid>http://tc.eserver.org/30417.html</guid>
		<description>By developing a strategic plan, finding out if we are  producing the right learning products in the most  efficient way, and changing to a minimalist document design, we can meet the challenges of the present business environment. Since many of us are  now expected to produce more with less while  maintaining or improving the quality of the products we produce, we need to manage our function better. By following the suggestions in this paper, you will be able to: communicate the importance of your function; get control of your function; demonstrate how you add value to your companies&apos; products.</description>
	</item>
	<item>
		<title>Essential Ingredients for Success in a Quality Improvement Program</title>
		<link>http://tc.eserver.org/29645.html</link>
		<guid>http://tc.eserver.org/29645.html</guid>
		<description>This paper describes what we learned during the development and implementation of a quality improvement program in the Documentation Development Division at SAS Institute Inc. Our division includes 48 writers and 12 editors. What we learned is that a quality improvement program needs to preserve collegiality, be repeatable and improvable over time, and be part of an integrated effort to create and maintain documentation standards and guidelines.</description>
	</item>
	<item>
		<title>Quality Management in Software Development Projects</title>
		<link>http://tc.eserver.org/24338.html</link>
		<guid>http://tc.eserver.org/24338.html</guid>
		<description>How do you ensure that business software systems will be good quality, i.e. they will meet the business need and have few bugs? How might &apos;testing&apos; be perforned at the requiremenst and design stages?</description>
	</item>
	<item>
		<title>The High Cost of Quality</title>
		<link>http://tc.eserver.org/23384.html</link>
		<guid>http://tc.eserver.org/23384.html</guid>
		<description>Quality Systems (QS) have become essential for (inter-)national competition. Companies spend large amounts of money for &apos;measuring&apos; quality defined by national and international standards. Quality, however, is a value, and like creeds and ideologies values cannot be measured with scientific exactness and are difficult to control. Total Quality Management (TQM) and other standardized concepts take that idealistic dimension into account. Certification according to ISO 9000, for instance, covers only about 50% of a TQM implementation.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Articles/Management/Quality.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>