<?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: Excellent and Consistent Content Development through Agile and Scrum</title>
	<atom:link href="http://thecontentwrangler.com/2008/03/01/excellent_and_consistent_content_development_through_agile_and_scrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://thecontentwrangler.com/2008/03/01/excellent_and_consistent_content_development_through_agile_and_scrum/</link>
	<description>Content is a business asset worthy of being managed</description>
	<lastBuildDate>Fri, 18 May 2012 01:51:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Eric Kuhnen</title>
		<link>http://thecontentwrangler.com/2008/03/01/excellent_and_consistent_content_development_through_agile_and_scrum/comment-page-1/#comment-279</link>
		<dc:creator>Eric Kuhnen</dc:creator>
		<pubDate>Wed, 26 Mar 2008 14:27:43 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=366#comment-279</guid>
		<description>&lt;p&gt;Nancy,
&lt;/p&gt;
&lt;p&gt;
Let me know if you have any lessons-learned in adapting Agile methods to your content team.&#160; Ideally, you would able to establish an independent Scrum to prioritize and release deliverables that matter most to your customers.
&lt;/p&gt;
&lt;p&gt;
Thanks,
&lt;/p&gt;
&lt;p&gt;
Eric
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Nancy,
</p>
<p>
Let me know if you have any lessons-learned in adapting Agile methods to your content team.&nbsp; Ideally, you would able to establish an independent Scrum to prioritize and release deliverables that matter most to your customers.
</p>
<p>
Thanks,
</p>
<p>
Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nancy</title>
		<link>http://thecontentwrangler.com/2008/03/01/excellent_and_consistent_content_development_through_agile_and_scrum/comment-page-1/#comment-278</link>
		<dc:creator>Nancy</dc:creator>
		<pubDate>Tue, 25 Mar 2008 06:26:38 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=366#comment-278</guid>
		<description>&lt;p&gt;Hi,
&lt;/p&gt;
&lt;p&gt;
Excellent article - I really appreciate your knowledge about Agile methods to content writers, I have bookmarked it for later viewing and forwarded it on.
&lt;/p&gt;
&lt;p&gt;
Cheers.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hi,
</p>
<p>
Excellent article &#8211; I really appreciate your knowledge about Agile methods to content writers, I have bookmarked it for later viewing and forwarded it on.
</p>
<p>
Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Kuhnen</title>
		<link>http://thecontentwrangler.com/2008/03/01/excellent_and_consistent_content_development_through_agile_and_scrum/comment-page-1/#comment-277</link>
		<dc:creator>Eric Kuhnen</dc:creator>
		<pubDate>Wed, 19 Mar 2008 20:57:38 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=366#comment-277</guid>
		<description>&lt;p&gt;Virginia,
&lt;/p&gt;
&lt;p&gt;
An executable example is the perfect kind of documentation.&#160; As another example of good documentation, the on-line help given for Microsoft Excel has been very informative without being verbose, in part because it contains some excellent examples for each of the functions.
&lt;/p&gt;
&lt;p&gt;
Thanks for your comments.
&lt;/p&gt;
&lt;p&gt;
Eric
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Virginia,
</p>
<p>
An executable example is the perfect kind of documentation.&nbsp; As another example of good documentation, the on-line help given for Microsoft Excel has been very informative without being verbose, in part because it contains some excellent examples for each of the functions.
</p>
<p>
Thanks for your comments.
</p>
<p>
Eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Virginia O'Connor</title>
		<link>http://thecontentwrangler.com/2008/03/01/excellent_and_consistent_content_development_through_agile_and_scrum/comment-page-1/#comment-276</link>
		<dc:creator>Virginia O'Connor</dc:creator>
		<pubDate>Tue, 18 Mar 2008 20:22:03 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=366#comment-276</guid>
		<description>&lt;p&gt;Eric,
&lt;/p&gt;
&lt;p&gt;
I particularly liked the Content Development Manifesto. We&#8217;ve found the implementation of executable examples to be one of the most often used supporting content in our plug-in. So much, in fact, that I hear immediately when one of them doesn&#8217;t work quite right! &lt;img src=&quot;http://thecontentwrangler.com/images/smileys/grin.gif&quot; width=&quot;19&quot; height=&quot;19&quot; alt=&quot;grin&quot; style=&quot;border:0;&quot; /&gt; No worries, it&#8217;s all good collaboration and feedback.
&lt;/p&gt;
&lt;p&gt;
Anyway, I really liked how you related the Agile methods to content writers - well done and thanks!
&lt;/p&gt;
&lt;p&gt;
Virginia
&lt;br /&gt;
&lt;a href=&quot;http://www.xaware.org&quot; rel=&quot;nofollow&quot;&gt;http://www.xaware.org&lt;/a&gt;
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Eric,
</p>
<p>
I particularly liked the Content Development Manifesto. We&#8217;ve found the implementation of executable examples to be one of the most often used supporting content in our plug-in. So much, in fact, that I hear immediately when one of them doesn&#8217;t work quite right! <img src="http://thecontentwrangler.com/images/smileys/grin.gif" width="19" height="19" alt="grin" style="border:0;" /> No worries, it&#8217;s all good collaboration and feedback.
</p>
<p>
Anyway, I really liked how you related the Agile methods to content writers &#8211; well done and thanks!
</p>
<p>
Virginia<br />
<br />
<a href="http://www.xaware.org" rel="nofollow">http://www.xaware.org</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Wethington</title>
		<link>http://thecontentwrangler.com/2008/03/01/excellent_and_consistent_content_development_through_agile_and_scrum/comment-page-1/#comment-275</link>
		<dc:creator>Mike Wethington</dc:creator>
		<pubDate>Wed, 12 Mar 2008 18:05:36 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=366#comment-275</guid>
		<description>&lt;p&gt;If your interested in discussing Scrum, Agile, and the doc writing process, join us at the agile development and technical communications group.
&lt;br /&gt;
&lt;a href=&quot;http://thecontentwrangler.ning.com/group/agiledevelopmentandtechnicalcommunications&quot; rel=&quot;nofollow&quot;&gt;http://thecontentwrangler.ning.com/group/agiledevelopmentandtechnicalcommunications&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
Hope to see you there!
&lt;br /&gt;
Mike
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>If your interested in discussing Scrum, Agile, and the doc writing process, join us at the agile development and technical communications group.<br />
<br />
<a href="http://thecontentwrangler.ning.com/group/agiledevelopmentandtechnicalcommunications" rel="nofollow">http://thecontentwrangler.ning.com/group/agiledevelopmentandtechnicalcommunications</a>
</p>
<p>
Hope to see you there!<br />
<br />
Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Kuhnen</title>
		<link>http://thecontentwrangler.com/2008/03/01/excellent_and_consistent_content_development_through_agile_and_scrum/comment-page-1/#comment-274</link>
		<dc:creator>Eric Kuhnen</dc:creator>
		<pubDate>Mon, 03 Mar 2008 17:20:19 +0000</pubDate>
		<guid isPermaLink="false">http://localhost:8888/ee/?p=366#comment-274</guid>
		<description>&lt;p&gt;The section after &#8220;AUTHOR&#8217;S NOTE&#8221; was cut-off.&#160; It reads:
&lt;/p&gt;
&lt;p&gt;
The argument for a technical support person to be the product owner for technical documentation may be off-kilter.&#160; After all, a Product Manager is responsible for the whole product, which includes both software and documentation, so it seems more natural to have this person be the product owner for the technical documentation.&#160; However, my professional experience includes several years as a software developer, a product manager, and a technical support engineer.&#160; In surveying that experience, I find myself recalling a lot of customer frustration on the telephone because the product documentation was poorly written.&#160; Hence, while it is counter-intuitive thinking, I find myself trusting the judgment of a technical support engineer more than I trust the judgment of a detached Product Manager to know what kind of technical documentation the customer needs to read.&#160; Your experience may be different and so you may think differently on this point.
&lt;/p&gt;
&lt;p&gt;
Sorry for the omission.
&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>The section after &#8220;AUTHOR&#8217;S NOTE&#8221; was cut-off.&nbsp; It reads:
</p>
<p>
The argument for a technical support person to be the product owner for technical documentation may be off-kilter.&nbsp; After all, a Product Manager is responsible for the whole product, which includes both software and documentation, so it seems more natural to have this person be the product owner for the technical documentation.&nbsp; However, my professional experience includes several years as a software developer, a product manager, and a technical support engineer.&nbsp; In surveying that experience, I find myself recalling a lot of customer frustration on the telephone because the product documentation was poorly written.&nbsp; Hence, while it is counter-intuitive thinking, I find myself trusting the judgment of a technical support engineer more than I trust the judgment of a detached Product Manager to know what kind of technical documentation the customer needs to read.&nbsp; Your experience may be different and so you may think differently on this point.
</p>
<p>
Sorry for the omission.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

