<?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: Embedded Systems Conference FAQ</title>
	<atom:link href="http://www.renaissancesoftware.net/blog/archives/14/feed" rel="self" type="application/rss+xml" />
	<link>http://www.renaissancesoftware.net/blog/archives/14</link>
	<description>Blogging about Agile Development, especially embedded.  Follow me on twitter: jwgrenning</description>
	<lastBuildDate>Thu, 02 Feb 2012 07:09:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Janet Gregory</title>
		<link>http://www.renaissancesoftware.net/blog/archives/14/comment-page-1#comment-339</link>
		<dc:creator>Janet Gregory</dc:creator>
		<pubDate>Tue, 24 Feb 2009 18:02:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.renaissancesoftware.net/blog/?p=14#comment-339</guid>
		<description>Another question I ask teams about documentation besides the &quot;What is the purpose?&quot;, is &quot;Who is the audience?&quot;. Sometimes the team understands what it is supposed to do, but if you actually look at who it is getting it, there is a disconnect and the document adds no real value.

I like the &#039;as built&#039; documentation too, and have written story cards so that the time is accounted for. If it is truly necessary, it will get prioritized by the customer.</description>
		<content:encoded><![CDATA[<p>Another question I ask teams about documentation besides the &#8220;What is the purpose?&#8221;, is &#8220;Who is the audience?&#8221;. Sometimes the team understands what it is supposed to do, but if you actually look at who it is getting it, there is a disconnect and the document adds no real value.</p>
<p>I like the &#8216;as built&#8217; documentation too, and have written story cards so that the time is accounted for. If it is truly necessary, it will get prioritized by the customer.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

