<?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"
	>
<channel>
	<title>Comments on: Documentation is No Substitute for Interaction</title>
	<atom:link href="http://jonathanbabcock.com/2008/05/13/documentation-is-no-substitute-for-interaction/feed" rel="self" type="application/rss+xml" />
	<link>http://jonathanbabcock.com/2008/05/13/documentation-is-no-substitute-for-interaction/</link>
	<description>Business Analysis &#124; Software Methodology &#124; Process Improvement</description>
	<pubDate>Wed, 15 Oct 2008 23:02:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: JB</title>
		<link>http://jonathanbabcock.com/2008/05/13/documentation-is-no-substitute-for-interaction/#comment-789</link>
		<dc:creator>JB</dc:creator>
		<pubDate>Thu, 22 May 2008 01:17:21 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanbabcock.com/?p=215#comment-789</guid>
		<description>Thanks, Bill. 

I am feeling your comment Re: "following process for process sake."  I still run into projects occasionally where it seems like we are holding up the works by making sure that all the i's are dotted and t's crossed and all sections of every document full of verbiage just to follow process.

As a BA, no one values good, solid documentation more than I, but the trick seems to be learning to document "just enough" and then move on. More isn't necessarily better.</description>
		<content:encoded><![CDATA[<p>Thanks, Bill. </p>
<p>I am feeling your comment Re: &#8220;following process for process sake.&#8221;  I still run into projects occasionally where it seems like we are holding up the works by making sure that all the i&#8217;s are dotted and t&#8217;s crossed and all sections of every document full of verbiage just to follow process.</p>
<p>As a BA, no one values good, solid documentation more than I, but the trick seems to be learning to document &#8220;just enough&#8221; and then move on. More isn&#8217;t necessarily better.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill</title>
		<link>http://jonathanbabcock.com/2008/05/13/documentation-is-no-substitute-for-interaction/#comment-773</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Wed, 14 May 2008 04:06:02 +0000</pubDate>
		<guid isPermaLink="false">http://jonathanbabcock.com/?p=215#comment-773</guid>
		<description>JB, Nice post.  I happen to agree.  It's the understanding of the need that's most important, and the documentation helps to confirm that what was communicated was understood.

A similar mistake is made in process where process is followed for process sake rather than to facilitate the production of product.

I do believe, however, that the BA can serve as a substitute for the customer with the developers.</description>
		<content:encoded><![CDATA[<p>JB, Nice post.  I happen to agree.  It&#8217;s the understanding of the need that&#8217;s most important, and the documentation helps to confirm that what was communicated was understood.</p>
<p>A similar mistake is made in process where process is followed for process sake rather than to facilitate the production of product.</p>
<p>I do believe, however, that the BA can serve as a substitute for the customer with the developers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
