<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Suggestions for Survival in an Agile Environment as a Technical Communicator</title>
	<atom:link href="http://www.gryphonmountain.net/2009/04/suggestions-for-survival-in-an-agile-environment-as-a-technical-communicator/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gryphonmountain.net/2009/04/suggestions-for-survival-in-an-agile-environment-as-a-technical-communicator/</link>
	<description>Technical Communication and Other Writing Topics (by Ben Minson)</description>
	<lastBuildDate>Thu,  9 Sep 2010 15:59:36 -0500</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Ben</title>
		<link>http://www.gryphonmountain.net/2009/04/suggestions-for-survival-in-an-agile-environment-as-a-technical-communicator/comment-page-1/#comment-27787</link>
		<dc:creator>Ben</dc:creator>
		<pubDate>Wed, 13 May 2009 00:10:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=539#comment-27787</guid>
		<description>The first challenge that comes to mind is that multiple writers means more effort to keep everyone up to date on changes, but at the same time, more writers means more eyes and ears, and they can share information that one writer may otherwise have a harder time learning alone.Having multiple writers may also cause a challenge in spending time with the stakeholders or customers. You may need to have a lead writer represent the documentation team in communicating with the customers rather than all writers talking to the customers about their separate pieces of work.</description>
		<content:encoded><![CDATA[<p>The first challenge that comes to mind is that multiple writers means more effort to keep everyone up to date on changes, but at the same time, more writers means more eyes and ears, and they can share information that one writer may otherwise have a harder time learning alone.Having multiple writers may also cause a challenge in spending time with the stakeholders or customers. You may need to have a lead writer represent the documentation team in communicating with the customers rather than all writers talking to the customers about their separate pieces of work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vishnu</title>
		<link>http://www.gryphonmountain.net/2009/04/suggestions-for-survival-in-an-agile-environment-as-a-technical-communicator/comment-page-1/#comment-27730</link>
		<dc:creator>Vishnu</dc:creator>
		<pubDate>Tue, 12 May 2009 06:43:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=539#comment-27730</guid>
		<description>What challnges can Agile cause for documentation prepared by multiple technical writers?</description>
		<content:encoded><![CDATA[<p>What challnges can Agile cause for documentation prepared by multiple technical writers?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Albing</title>
		<link>http://www.gryphonmountain.net/2009/04/suggestions-for-survival-in-an-agile-environment-as-a-technical-communicator/comment-page-1/#comment-27204</link>
		<dc:creator>Bill Albing</dc:creator>
		<pubDate>Mon, 04 May 2009 18:49:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.gryphonmountain.net/?p=539#comment-27204</guid>
		<description>Yes, tags are definitely important, and it&#039;s a new discipline for many of us. I work in an agile development environment at Paragon and my skills at chunking information come in handy. Since the developers are delivering small chunks of functionality, I can develop small updates to the docs. With agile, we&#039;re all involved in the conversation with the customer (or customer advocate) and many of us are involved in testing, so I can see the functionality as it develops. Now we&#039;re making videos of the demos of the finished &quot;potentially shippable product&quot;, as the chunk is often called.</description>
		<content:encoded><![CDATA[<p>Yes, tags are definitely important, and it&#8217;s a new discipline for many of us. I work in an agile development environment at Paragon and my skills at chunking information come in handy. Since the developers are delivering small chunks of functionality, I can develop small updates to the docs. With agile, we&#8217;re all involved in the conversation with the customer (or customer advocate) and many of us are involved in testing, so I can see the functionality as it develops. Now we&#8217;re making videos of the demos of the finished &#8220;potentially shippable product&#8221;, as the chunk is often called.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
