<?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: Pairing Business Analysts</title>
	<atom:link href="http://tynerblain.com/blog/2006/11/20/pairing-business-analysts/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2006/11/20/pairing-business-analysts/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sun, 12 Feb 2012 19:10:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2006/11/20/pairing-business-analysts/comment-page-1/#comment-57248</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Fri, 24 Nov 2006 01:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/11/20/pairing-business-analysts/#comment-57248</guid>
		<description>Luis,

Great point about immediate reviews.

Interesting point about the lack of &quot;defined consistency rules&quot; for writing.  Do you think it is analogous to variations in coding style, or more like a lack of defined syntax?  

I completely agree about novels/artistic writing, and I could see how writing style (phrasing, grammar, etc) would make a document awkward to read if it changed on a regular basis throughout the document.  I know I struggle when reviewing someone else&#039;s writing, when it comes to stylistic feedback.  It is hard to avoid rewriting a paragraph that is &quot;ok, but not the way I would do it.&quot;  How do programmers deal with this when pairing?</description>
		<content:encoded><![CDATA[<p>Luis,</p>
<p>Great point about immediate reviews.</p>
<p>Interesting point about the lack of &#8220;defined consistency rules&#8221; for writing.  Do you think it is analogous to variations in coding style, or more like a lack of defined syntax?  </p>
<p>I completely agree about novels/artistic writing, and I could see how writing style (phrasing, grammar, etc) would make a document awkward to read if it changed on a regular basis throughout the document.  I know I struggle when reviewing someone else&#8217;s writing, when it comes to stylistic feedback.  It is hard to avoid rewriting a paragraph that is &#8220;ok, but not the way I would do it.&#8221;  How do programmers deal with this when pairing?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Sergio Oliveira</title>
		<link>http://tynerblain.com/blog/2006/11/20/pairing-business-analysts/comment-page-1/#comment-57118</link>
		<dc:creator>Luis Sergio Oliveira</dc:creator>
		<pubDate>Tue, 21 Nov 2006 06:33:05 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/11/20/pairing-business-analysts/#comment-57118</guid>
		<description>[e-mail corrected]</description>
		<content:encoded><![CDATA[<p>[e-mail corrected]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Luis Sergio Oliveira</title>
		<link>http://tynerblain.com/blog/2006/11/20/pairing-business-analysts/comment-page-1/#comment-57117</link>
		<dc:creator>Luis Sergio Oliveira</dc:creator>
		<pubDate>Tue, 21 Nov 2006 06:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2006/11/20/pairing-business-analysts/#comment-57117</guid>
		<description>I have experimented with pair authoring several times and it works very well.
It wasn&#039;t for requirements, but, in functional specifications.
I think I can sell it the same way I can sell the pair programming. Any work output that requires review, if made with a pair is immediately reviewed. From there comes the quality improvement and in the end the possible productivity improvement.

The downside for me is that contrary to programming, writing has no well defined consistency rules for prose and schematics&#039; style. So, you may loose in the way a &quot;document feels&quot;. This isn&#039;t so serious in technical documentation as it is in novels or more artistic writings...</description>
		<content:encoded><![CDATA[<p>I have experimented with pair authoring several times and it works very well.<br />
It wasn&#8217;t for requirements, but, in functional specifications.<br />
I think I can sell it the same way I can sell the pair programming. Any work output that requires review, if made with a pair is immediately reviewed. From there comes the quality improvement and in the end the possible productivity improvement.</p>
<p>The downside for me is that contrary to programming, writing has no well defined consistency rules for prose and schematics&#8217; style. So, you may loose in the way a &#8220;document feels&#8221;. This isn&#8217;t so serious in technical documentation as it is in novels or more artistic writings&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

