<?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;Collaboration</title>	<link>http://tc.eserver.org/dir/Presentations/Management/Collaboration</link>
	<description>A listing of the most recently indexed works about Presentations and Management and Collaboration 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;Collaboration</title>
		<link>http://tc.eserver.org/dir/Presentations/Management/Collaboration</link>
	</image>
	<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>Communicating with Upper Management</title>
		<link>http://tc.eserver.org/28755.html</link>
		<guid>http://tc.eserver.org/28755.html</guid>
		<description>What is your greatest challenge in communicating with your upper management?</description>
	</item>
	<item>
		<title>It&apos;s about the Community Plumbing: The Social Aspects of Content Management Systems</title>
		<link>http://tc.eserver.org/26496.html</link>
		<guid>http://tc.eserver.org/26496.html</guid>
		<description>In the summer of 2003, we worked on creating a general description of Drupal--an open source content management system (CMS)--for the &quot;About Drupal&quot; page on drupal.org. While Drupal is clearly within the class of applications known as content management systems, we felt that to describe it with that term alone would not present a clear picture of the breadth and range of Drupal&apos;s capabilities. Thus, the final description ended up describing Drupal with a total of four characteristics, although notably not distinct content management; weblog; discussion-based community software; and collaboration.&#xD;&#xD;Why is it then that the term CMS alone would not suffice? The word &quot;content&quot; places much emphasis on the product over process; it fails to emphasize the social use of CMSes, a mislabeling which places too much emphasis on the content itself at the expense of the communication and collaboration the better of these systems implement. In order to better understand how CMSes are being influenced by the precepts of social software and their role in creating social networks online, this presentation will: explore Drupal&apos;s social software features, narrate its genesis as software serving a community; and explain the influence of the community itself on Drupal development and the software&apos;s influence on the community that creates and uses it.&#xD;&#xD;In composing this text, we draw on the coauthors&apos; unique perspectives. One of us is the founder and lead developer of Drupal, and the other a researcher in Computers and Writing and a participant in the Drupal community.</description>
	</item>
	<item>
		<title>Developing a Content Management Team for Your Intranet</title>
		<link>http://tc.eserver.org/23936.html</link>
		<guid>http://tc.eserver.org/23936.html</guid>
		<description>What is the overall process?  Who are the players? What are their best uses?</description>
	</item>
	<item>
		<title>Making Your Team Work</title>
		<link>http://tc.eserver.org/20948.html</link>
		<guid>http://tc.eserver.org/20948.html</guid>
		<description>This presentation looks at some of the common pitfalls that first-time&#xD;technical communication managers encounter, and discusses how this&#xD;affects the effectiveness of both managers and their teams, and hopes to&#xD;spark a debate about alternative management styles.</description>
	</item>
	<item>
		<title>Managing a Distributed Documentation Group</title>
		<link>http://tc.eserver.org/18265.html</link>
		<guid>http://tc.eserver.org/18265.html</guid>
		<description>A distributed documentation group is one in which&#xD;people work together from distant locations, The new&#xD;problem in managing such a group is that casual, face-to-face&#xD;communication is missing. Technological&#xD;solutions include source control, email, groupware,&#xD;telephone, and the World Wide Web. Human solutions&#xD;may be even more important. Autonomy, explicit&#xD;standards, various ways to meet, and deliberately&#xD;working across locations build the necessary&#xD;communications and trust.</description>
	</item>
	<item>
		<title>Taming a Telecommuting Team</title>
		<link>http://tc.eserver.org/18264.html</link>
		<guid>http://tc.eserver.org/18264.html</guid>
		<description>“Telecommuting” includes situations where members of a&#xD;group (department, team, other) are working in different&#xD;locations, communicating with each other and with clients&#xD;by phone, fax, and e-mail. The team may be dispersed&#xD;through an urban area, nationally, or internationally.&#xD;Telecommuting has advantages and disadvantages over&#xD;the traditional centralized working group and presents new&#xD;challenges to management and staff As a team leader of&#xD;telecommuting technical writers on software development&#xD;projects, I have dealt with many of these Issues. In this&#xD;discussion I cover some of the advantages and&#xD;disadvantages and some principles and rules of successful&#xD;telecommuting teams.&#xD;</description>
	</item>
	<item>
		<title>Collaborative Writing In Segmentalist Organizations: Commitments For Team Success</title>
		<link>http://tc.eserver.org/14538.html</link>
		<guid>http://tc.eserver.org/14538.html</guid>
		<description>Many large, hierarchical organizations are&#xD;segmentalist in their approach to management.&#xD;Nonetheless, such organizations are capable of&#xD;supporting integrated, team approaches to particular&#xD;types of communication problems. For such&#xD;approaches to be successful, however, there must be&#xD;strong managerial commitments to team support. This&#xD;paper discusses how committed leadership, specific&#xD;production guidelines, and empowerment enhanced&#xD;the activities of an Air Force writing team assembled&#xD;to help revise and edit Air Force Policy Directives&#xD;containing corporate level guidance on a variety of&#xD;topics.</description>
	</item>
	<item>
		<title>Breaking Up Is Hard to Do: Decentralizing a Doc Group</title>
		<link>http://tc.eserver.org/14385.html</link>
		<guid>http://tc.eserver.org/14385.html</guid>
		<description>Re-engineering — a word that strikes fear into the hearts of middle-management. Our company was hit by reengineering&#xD;fever in 1995–6, and word came down that&#xD;we were to break up our comfortable little documentation&#xD;group and distribute the writers among product&#xD;development teams. We did it, and we did it right. In this&#xD;paper, we&#xD;· Review the thinking and planning that went into the&#xD;conversion of a 30-person, centralized, corporatewide&#xD;documentation group into a decentralized,&#xD;loosely affiliated community of technical writers.&#xD;· Describe the implementation of our plans and some&#xD;of the pitfalls we encountered and overcame.&#xD;· Share an evaluation of the success of the reorganization,&#xD;and some tips that we learned along&#xD;the way.</description>
	</item>
	<item>
		<title>Thriving Teams</title>
		<link>http://tc.eserver.org/13686.html</link>
		<guid>http://tc.eserver.org/13686.html</guid>
		<description>We are going to examine the similarity between a well-functioning body and a thriving team. Specifically we’ll look be looking at balance, coordination, and growth. There are enough parallels in these three categories to show how when a team is treated the same way we treat our bodies we end up with similar results.</description>
	</item>
	<item>
		<title>When Things Go Wrong: Working Toward Perfection While Accepting Imperfection</title>
		<link>http://tc.eserver.org/13471.html</link>
		<guid>http://tc.eserver.org/13471.html</guid>
		<description>Come to terms with unavoidable human errors by freeing yourself of panic, discovering new ways to solve the problems caused, and devising new procedures to prevent future mistakes.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Presentations/Management/Collaboration.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>