<?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: Multi-site teams: travel and the half life of trust</title>
	<atom:link href="http://leansoftwareengineering.com/2009/08/06/multi-site-teams-travel-and-the-half-life-of-trust/feed/" rel="self" type="application/rss+xml" />
	<link>http://leansoftwareengineering.com/2009/08/06/multi-site-teams-travel-and-the-half-life-of-trust/</link>
	<description>Essays on the Continuous Delivery of High Quality Information Systems</description>
	<lastBuildDate>Mon, 22 Feb 2010 09:08:24 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Bernie Thompson</title>
		<link>http://leansoftwareengineering.com/2009/08/06/multi-site-teams-travel-and-the-half-life-of-trust/comment-page-1/#comment-6139</link>
		<dc:creator>Bernie Thompson</dc:creator>
		<pubDate>Fri, 30 Oct 2009 17:25:57 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/?p=1951#comment-6139</guid>
		<description>Hi Matthias - very good point.  And, in fact, where you do have &quot;teams&quot; within open source - usually people working for Canonical vs. Red Hat vs. Intel, etc. -- those tensions and &quot;us vs. them&quot; feelings definitely rear their heads (e.g. see http://video.google.com/videoplay?docid=3385088017824733336 ) The &quot;pressure valve&quot; is the choice to (at least temporarily) branch and deliver competing versions -- even if it&#039;s not always the right thing for the technology or for the end-user. And that happens all the time in Open Source. Commercial companies tend to force their teams to deliver just one thing.</description>
		<content:encoded><![CDATA[<p>Hi Matthias &#8211; very good point.  And, in fact, where you do have &#8220;teams&#8221; within open source &#8211; usually people working for Canonical vs. Red Hat vs. Intel, etc. &#8212; those tensions and &#8220;us vs. them&#8221; feelings definitely rear their heads (e.g. see <a href="http://video.google.com/videoplay?docid=3385088017824733336" rel="nofollow">http://video.google.com/videop.....7824733336</a> ) The &#8220;pressure valve&#8221; is the choice to (at least temporarily) branch and deliver competing versions &#8212; even if it&#8217;s not always the right thing for the technology or for the end-user. And that happens all the time in Open Source. Commercial companies tend to force their teams to deliver just one thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matthias Marschall</title>
		<link>http://leansoftwareengineering.com/2009/08/06/multi-site-teams-travel-and-the-half-life-of-trust/comment-page-1/#comment-6071</link>
		<dc:creator>Matthias Marschall</dc:creator>
		<pubDate>Fri, 11 Sep 2009 08:36:04 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/?p=1951#comment-6071</guid>
		<description>There is one important difference between open source projects and corporate settings that is often overlooked.

In an open source project you usually have _individuals_ working together whereas in corporate settings, you usually have _teams_.

In my experience it is very important to understand the team dynamics at all locations as they re-enforce the &quot;us vs them&quot; feelings.</description>
		<content:encoded><![CDATA[<p>There is one important difference between open source projects and corporate settings that is often overlooked.</p>
<p>In an open source project you usually have _individuals_ working together whereas in corporate settings, you usually have _teams_.</p>
<p>In my experience it is very important to understand the team dynamics at all locations as they re-enforce the &#8220;us vs them&#8221; feelings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dew Drop &#8211; August 7, 2009 &#124; Alvin Ashcraft's Morning Dew</title>
		<link>http://leansoftwareengineering.com/2009/08/06/multi-site-teams-travel-and-the-half-life-of-trust/comment-page-1/#comment-6020</link>
		<dc:creator>Dew Drop &#8211; August 7, 2009 &#124; Alvin Ashcraft's Morning Dew</dc:creator>
		<pubDate>Fri, 07 Aug 2009 12:12:24 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/?p=1951#comment-6020</guid>
		<description>[...] Multi-site teams: travel and the half life of trust (Bernie Thompson) [...]</description>
		<content:encoded><![CDATA[<p>[...] Multi-site teams: travel and the half life of trust (Bernie Thompson) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.504 seconds -->
<!-- Cached page served by WP-Cache -->
