<?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: Distributed Scrum</title>
	<atom:link href="http://kanemar.com/2009/01/27/distributed-scrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://kanemar.com/2009/01/27/distributed-scrum/</link>
	<description>Adventures in Agile Software Development and Scrum</description>
	<lastBuildDate>Thu, 19 Apr 2012 09:24:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Barbara Brown</title>
		<link>http://kanemar.com/2009/01/27/distributed-scrum/#comment-13945</link>
		<dc:creator><![CDATA[Barbara Brown]]></dc:creator>
		<pubDate>Wed, 03 Mar 2010 04:35:09 +0000</pubDate>
		<guid isPermaLink="false">http://kanemar.wordpress.com/?p=370#comment-13945</guid>
		<description><![CDATA[Kane:

I&#039;ve been using distributed scrum for almost 2 years. It takes some rigor, but I feel it works just as well (or, on occasion, poorly!) as co-located scrum. 

The keys to our team structure are: 1) rigorous enforcement of daily standup -- usually somewhat uncomfortably early in the a.m. for the Seattle-ites, somewhat uncomfortably late for our European/East Coast team time zones; 2) shared code base - no one develops extensively locally and expects to check in code; 3) continuous build environment - when it breaks, you fix it right away! 4) clear handoffs of tasks to the teams who will be awake in the next hours.

Another trick we use is opening up a group chat so we&#039;re all solving problems together -- not individual emails/calls flying around where half of us are in the know and half are out.

It&#039;s not perfect -- what is?! But I think distributed agile teams are the way of the world going forward, so we need to figure out how to make it work. I think it&#039;s worked for us.

Thanks!
Barbara]]></description>
		<content:encoded><![CDATA[<p>Kane:</p>
<p>I&#8217;ve been using distributed scrum for almost 2 years. It takes some rigor, but I feel it works just as well (or, on occasion, poorly!) as co-located scrum. </p>
<p>The keys to our team structure are: 1) rigorous enforcement of daily standup &#8212; usually somewhat uncomfortably early in the a.m. for the Seattle-ites, somewhat uncomfortably late for our European/East Coast team time zones; 2) shared code base &#8211; no one develops extensively locally and expects to check in code; 3) continuous build environment &#8211; when it breaks, you fix it right away! 4) clear handoffs of tasks to the teams who will be awake in the next hours.</p>
<p>Another trick we use is opening up a group chat so we&#8217;re all solving problems together &#8212; not individual emails/calls flying around where half of us are in the know and half are out.</p>
<p>It&#8217;s not perfect &#8212; what is?! But I think distributed agile teams are the way of the world going forward, so we need to figure out how to make it work. I think it&#8217;s worked for us.</p>
<p>Thanks!<br />
Barbara</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David</title>
		<link>http://kanemar.com/2009/01/27/distributed-scrum/#comment-13646</link>
		<dc:creator><![CDATA[David]]></dc:creator>
		<pubDate>Sat, 28 Feb 2009 11:05:35 +0000</pubDate>
		<guid isPermaLink="false">http://kanemar.wordpress.com/?p=370#comment-13646</guid>
		<description><![CDATA[Follow the sun approaches have always been an interesting concept, however it is a concept that needs to be implemented correctly. As you have mentioned, factors such as communication, common code bases etc need to be considered.
I think if it was planned carefully, distributed Scrum could work. The only real issue is real communication between the teams. As it is a follow the sun approach, questions have to be asked, then wait for another day for the response.

Regards,
David
jacksguides.com]]></description>
		<content:encoded><![CDATA[<p>Follow the sun approaches have always been an interesting concept, however it is a concept that needs to be implemented correctly. As you have mentioned, factors such as communication, common code bases etc need to be considered.<br />
I think if it was planned carefully, distributed Scrum could work. The only real issue is real communication between the teams. As it is a follow the sun approach, questions have to be asked, then wait for another day for the response.</p>
<p>Regards,<br />
David<br />
jacksguides.com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: GettingAgile.com &#187; Blog Archive &#187; Distributed Scrum</title>
		<link>http://kanemar.com/2009/01/27/distributed-scrum/#comment-13619</link>
		<dc:creator><![CDATA[GettingAgile.com &#187; Blog Archive &#187; Distributed Scrum]]></dc:creator>
		<pubDate>Wed, 28 Jan 2009 16:12:11 +0000</pubDate>
		<guid isPermaLink="false">http://kanemar.wordpress.com/?p=370#comment-13619</guid>
		<description><![CDATA[[...] Kane Mar describes patterns in distributed teams and Scrum from his experience in this article. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Kane Mar describes patterns in distributed teams and Scrum from his experience in this article. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

