<?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: Collaborate! But not with you&#8230;</title>
	<atom:link href="http://www.adeptechllc.com/2008/06/19/collaborate-but-not-with-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.adeptechllc.com/2008/06/19/collaborate-but-not-with-you/</link>
	<description>Software, Agile Process and Security</description>
	<lastBuildDate>Wed, 11 Aug 2010 03:38:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Keith McMillan</title>
		<link>http://www.adeptechllc.com/2008/06/19/collaborate-but-not-with-you/comment-page-1/#comment-4597</link>
		<dc:creator>Keith McMillan</dc:creator>
		<pubDate>Fri, 20 Jun 2008 12:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=114#comment-4597</guid>
		<description>I understand your concern.  It&#039;s one of the reasons that you delay talking about something until you&#039;re ready to do it, so your understanding is &quot;fresh&quot;, and get frequent and early feedback, so you avoid &quot;that&#039;s not what I meant.&quot;

What we find is if you need to write it down, you should do so after you&#039;ve discussed it, and that&#039;s only if someone who&#039;s not part of the collaboration needs it (like, say, the guy who will someday in the future support it).</description>
		<content:encoded><![CDATA[<p>I understand your concern.  It&#8217;s one of the reasons that you delay talking about something until you&#8217;re ready to do it, so your understanding is &#8220;fresh&#8221;, and get frequent and early feedback, so you avoid &#8220;that&#8217;s not what I meant.&#8221;</p>
<p>What we find is if you need to write it down, you should do so after you&#8217;ve discussed it, and that&#8217;s only if someone who&#8217;s not part of the collaboration needs it (like, say, the guy who will someday in the future support it).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Kailhofer</title>
		<link>http://www.adeptechllc.com/2008/06/19/collaborate-but-not-with-you/comment-page-1/#comment-4596</link>
		<dc:creator>Andy Kailhofer</dc:creator>
		<pubDate>Thu, 19 Jun 2008 20:32:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.adeptechllc.com/?p=114#comment-4596</guid>
		<description>My biggest concern is that a talking process that is not a documenting process leads to misunderstandings and you really need to write it down anyway (and have everybody agree that was what everybody meant) so you can be clear as to who meant what after the fact. I can&#039;t hold all the requirments in my head, I know I can&#039;t. I suppose I shouldn&#039;t expect people to be able express what they mean in written english any more than they can express it in verbally...</description>
		<content:encoded><![CDATA[<p>My biggest concern is that a talking process that is not a documenting process leads to misunderstandings and you really need to write it down anyway (and have everybody agree that was what everybody meant) so you can be clear as to who meant what after the fact. I can&#8217;t hold all the requirments in my head, I know I can&#8217;t. I suppose I shouldn&#8217;t expect people to be able express what they mean in written english any more than they can express it in verbally&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
