<?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: Using Timespans to Solve Communication Problems</title>
	<atom:link href="http://www.manasclerk.com/blog/2009/10/24/using-timespans-to-solve-communication-problems/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.manasclerk.com/blog/2009/10/24/using-timespans-to-solve-communication-problems/</link>
	<description>Because the killer app is us.</description>
	<lastBuildDate>Sun, 05 Feb 2012 06:16:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Can &#8220;Strategic&#8221; Mean Differrent Things to Software Architects? &#171; Hez Sez</title>
		<link>http://www.manasclerk.com/blog/2009/10/24/using-timespans-to-solve-communication-problems/#comment-29650</link>
		<dc:creator>Can &#8220;Strategic&#8221; Mean Differrent Things to Software Architects? &#171; Hez Sez</dc:creator>
		<pubDate>Wed, 09 Dec 2009 21:39:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.manasclerk.com/blog/?p=1061#comment-29650</guid>
		<description>[...] This guys says that a lot of it has to do with timespan of the term. He says that the problem is that we use terms like &#8220;long-term&#8221; and &#8220;strategic&#8221; in our software architecture discussions. He encountered the same thing we have when he had to document an enterprise architecture plan. The architects were from all over, and had very different ideas about what &#8220;long-term&#8221;,&#8221;short-term&#8221;, &#8220;strategic&#8221; and &#8220;tactical&#8221; meant: It turned out that they were disagreeing because they were all talking about different things. Some of them thought that the future state was 2 years out. Some thought it was 3 years out. A handful said 4-5. [...]</description>
		<content:encoded><![CDATA[<p>[...] This guys says that a lot of it has to do with timespan of the term. He says that the problem is that we use terms like &#8220;long-term&#8221; and &#8220;strategic&#8221; in our software architecture discussions. He encountered the same thing we have when he had to document an enterprise architecture plan. The architects were from all over, and had very different ideas about what &#8220;long-term&#8221;,&#8221;short-term&#8221;, &#8220;strategic&#8221; and &#8220;tactical&#8221; meant: It turned out that they were disagreeing because they were all talking about different things. Some of them thought that the future state was 2 years out. Some thought it was 3 years out. A handful said 4-5. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

