<?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: Documents vs. Conversations</title>
	<atom:link href="http://third-bit.com/blog/archives/332.html/feed" rel="self" type="application/rss+xml" />
	<link>http://third-bit.com/blog/archives/332.html</link>
	<description>Data is ones and zeroes &#124; Software is ones and zeroes and hard work.</description>
	<lastBuildDate>Thu, 24 May 2012 15:30:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://third-bit.com/blog/archives/332.html#comment-295</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 27 Dec 2005 23:55:41 +0000</pubDate>
		<guid isPermaLink="false">http://pyre.third-bit.com/blog/?p=332#comment-295</guid>
		<description>Conversations are critically important to defining requirements, but once the requirements are defined, the genesis of the spec is less relevant than the context of the spec.  I&#039;ve posted an article looking at the application of this idea, Managing requirements conversations (tynerblain.wordpress.com/2005/12/27/managing-requirements-conversations/)

I think you&#039;ll find it a good read.
Scott</description>
		<content:encoded><![CDATA[<p>Conversations are critically important to defining requirements, but once the requirements are defined, the genesis of the spec is less relevant than the context of the spec.  I&#8217;ve posted an article looking at the application of this idea, Managing requirements conversations (tynerblain.wordpress.com/2005/12/27/managing-requirements-conversations/)</p>
<p>I think you&#8217;ll find it a good read.<br />
Scott</p>
]]></content:encoded>
	</item>
</channel>
</rss>

