<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
	<title>Careers&gt;Collaboration&gt;Project Management</title>	<link>http://tc.eserver.org/dir/Careers/Collaboration/Project-Management</link>
	<description>A listing of the most recently indexed works about Careers and Collaboration and Project Management 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>Careers&gt;Collaboration&gt;Project Management</title>
		<link>http://tc.eserver.org/dir/Careers/Collaboration/Project-Management</link>
	</image>
	<item>
		<title>Keep Pesky Business Types at Bay by Focusing on the Strategic Goal</title>
		<link>http://tc.eserver.org/29373.html</link>
		<guid>http://tc.eserver.org/29373.html</guid>
		<description>If you have ever been forced to deal with business types who have no technical know-how, then you know how these types can work against IT&apos;s progress. Here&apos;s how to improve your business/IT communication by concentrating on the strategic goals.</description>
	</item>
	<item>
		<title>The Daily Stand-Up</title>
		<link>http://tc.eserver.org/27569.html</link>
		<guid>http://tc.eserver.org/27569.html</guid>
		<description>The first and most basic rhythm of the Agile feedback cycle is the daily standup. It&apos;s just what it sounds like - a daily meeting where everyone stands up for the duration of the meeting. When I give Agile workshops, one of the questions I&apos;m often asked is how to do daily standups when the teams are geographically dispersed. While this can be a challenge to coordinate and maintain, you&apos;ll soon find that the benefits of the daily communication make it well worth the effort. Here are several options to consider with your team:</description>
	</item>
	<item>
		<title>A Project Manager&apos;s Survival Guide to Going Agile</title>
		<link>http://tc.eserver.org/27562.html</link>
		<guid>http://tc.eserver.org/27562.html</guid>
		<description>This paper focuses on re-defining the job of project manager to better fit the self-managed team environment, one of the core agile principles. Special emphasis is placed on the shift to servant leadership, with its focus on facilitation and collaboration. Mapping of PMBOK knowledge areas to agile practices is discussed at length. After reading this paper, project managers should have a better understanding of what changes they need to make professionally, and how to make these changes in order to survive the transition to an agile software development approach.</description>
	</item>
	<item>
		<title>Handling Tough Situations: The Short Method</title>
		<link>http://tc.eserver.org/10220.html</link>
		<guid>http://tc.eserver.org/10220.html</guid>
		<description>We discussed how to buy time when you are assaulted by an unpleasant surprise. Our argument was that few people respond well to challenging situations unless they have some time to prepare. Therefore, whenever you can, you should divide the task into four distinct phases: (1) minimal immediate response, (2) preparation, (3) problem-solving discussion, and (4) follow-through. Unfortunately, some situations don&apos;t let you postpone a full discussion. For such cases, you need the &apos;short method,&apos; which condenses phases 1-3.</description>
	</item>
	<atom:link href="http://tc.eserver.org/dir/Careers/Collaboration/Project-Management.xml" rel="self" type="application/rss+xml"/>
</channel>
</rss>