<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: 7 tips for working with distributed teams.</title>
	<atom:link href="http://blog.brightgreenprojects.com/2009/10/21/7-tips-for-working-with-distributed-teams/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.brightgreenprojects.com/2009/10/21/7-tips-for-working-with-distributed-teams/</link>
	<description>a blog about agile project management, software development and business analysis.</description>
	<lastBuildDate>Fri, 18 Dec 2009 22:29:57 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Adam Feldman</title>
		<link>http://blog.brightgreenprojects.com/2009/10/21/7-tips-for-working-with-distributed-teams/#comment-125</link>
		<dc:creator>Adam Feldman</dc:creator>
		<pubDate>Fri, 06 Nov 2009 14:54:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brightgreenprojects.com/?p=196#comment-125</guid>
		<description>Svilen,

Sorry not to reply to your comment sooner! This is an absolutely fantastic point. I was once working on a project where we were based in the UK, however, our client was in Italy. We had huge cultural issues as the Italians were very vocal and really loud when voicing their concerns - many people in my team were actually quite upset.  After a few weeks, we organized a meeting to talk about these problems.  In the meeting the Italians gave us the feedback that they thought we were too quiet and not passionate enough about our work!

You are so, so right about the importance of this Svilen!</description>
		<content:encoded><![CDATA[<p>Svilen,</p>
<p>Sorry not to reply to your comment sooner! This is an absolutely fantastic point. I was once working on a project where we were based in the UK, however, our client was in Italy. We had huge cultural issues as the Italians were very vocal and really loud when voicing their concerns &#8211; many people in my team were actually quite upset.  After a few weeks, we organized a meeting to talk about these problems.  In the meeting the Italians gave us the feedback that they thought we were too quiet and not passionate enough about our work!</p>
<p>You are so, so right about the importance of this Svilen!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: svilen dobrev</title>
		<link>http://blog.brightgreenprojects.com/2009/10/21/7-tips-for-working-with-distributed-teams/#comment-99</link>
		<dc:creator>svilen dobrev</dc:creator>
		<pubDate>Thu, 29 Oct 2009 15:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brightgreenprojects.com/?p=196#comment-99</guid>
		<description>one more...  establish a common language. Not really a human language - think there are 1000s schools of teaching English, culturaly shaped, and then there is Singlish, Cinglish, ...
So a &quot;dictionary&quot; what each notion/term/gesture means, and insist on re/using that, tautologically if needed, in any talk/document/source-code about the work done.

Obvious? yeah, but it&#039;s difficult to apply/keep even in single-culture-single-team environment, how about cross-cultural-multi-team... hence most times left out. And Enter the Misunderstandings..</description>
		<content:encoded><![CDATA[<p>one more&#8230;  establish a common language. Not really a human language &#8211; think there are 1000s schools of teaching English, culturaly shaped, and then there is Singlish, Cinglish, &#8230;<br />
So a &#8220;dictionary&#8221; what each notion/term/gesture means, and insist on re/using that, tautologically if needed, in any talk/document/source-code about the work done.</p>
<p>Obvious? yeah, but it&#8217;s difficult to apply/keep even in single-culture-single-team environment, how about cross-cultural-multi-team&#8230; hence most times left out. And Enter the Misunderstandings..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: seven GSD tips &#171; GSD Collaboration</title>
		<link>http://blog.brightgreenprojects.com/2009/10/21/7-tips-for-working-with-distributed-teams/#comment-98</link>
		<dc:creator>seven GSD tips &#171; GSD Collaboration</dc:creator>
		<pubDate>Sat, 24 Oct 2009 05:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brightgreenprojects.com/?p=196#comment-98</guid>
		<description>[...] Leave a comment Go to comments    Found a recent blog post on the Bright Green Projects blogsite: 7 tips for working with distributed teams. A few of the tips are tool-specific (including one for their own product), but not all are; it [...]</description>
		<content:encoded><![CDATA[<p>[...] Leave a comment Go to comments    Found a recent blog post on the Bright Green Projects blogsite: 7 tips for working with distributed teams. A few of the tips are tool-specific (including one for their own product), but not all are; it [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
