<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Scrum Development Blog &#187; distributed agile development</title>
	<atom:link href="http://blog.3back.com/tag/distributed-agile-development/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.3back.com</link>
	<description>Better teams make better products.</description>
	<lastBuildDate>Thu, 02 Feb 2012 16:41:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Distributed Agile Teams</title>
		<link>http://blog.3back.com/scrum-industry-terms/distributed-agile-teams</link>
		<comments>http://blog.3back.com/scrum-industry-terms/distributed-agile-teams#comments</comments>
		<pubDate>Thu, 25 Feb 2010 21:36:29 +0000</pubDate>
		<dc:creator>The 3Back Team</dc:creator>
				<category><![CDATA[Scrum Terms]]></category>
		<category><![CDATA[distributed agile development]]></category>
		<category><![CDATA[Distributed Agile Teams]]></category>
		<category><![CDATA[Distributed Scrum Teams]]></category>

		<guid isPermaLink="false">http://blog.3back.com/?p=249</guid>
		<description><![CDATA[Distributed agile can work, but it is risky. Even more than traditional agile implementations, distributed teams tend to fall into two failure modes: “command as control” or team fragmentation. ]]></description>
			<content:encoded><![CDATA[<p><strong>Distributed agile teams</strong> can work, but it is risky. Even more than traditional agile implementations, distributed teams tend to fall into two failure modes: “command as control” or team fragmentation.</p>
<p><strong>Why?</strong></p>
<p>Agile methodologies warn how critical it is to co-locate teams in the same room, but this is not always practical. <a href="http://blog.3back.com/wp-content/uploads/2010/02/world-distributed-agile-scrum-teams.jpg"><img class="alignright size-full wp-image-250" title="world-distributed-agile-scrum-teams" src="http://blog.3back.com/wp-content/uploads/2010/02/world-distributed-agile-scrum-teams.jpg" alt="distributed agile teams" width="321" height="373" /></a>Distributed or “virtual” teams are a reality of business today.  Offshoring, flex-work schedules, multiple corporate offices, and other forces create pressures to achieve results even when team members are scattered across the globe.</p>
<p>But most of these distributed teams seem to prove the Agile warnings right by demonstrating old habits of waterfall behavior.  Long cycle times and endless requirements revision are the norm, status reporting takes up far too much time, and individual leaders dominate the team.  Management direction gets lost in a sea of process and tools instead of manifesting as tangible, quality product.</p>
<p>How can we realize the benefits of Agile product development – hyperproductivity, high-quality products, self-organization, elimination of waste, and rapid releases – when team members are not sitting next to each other? How do we make <a title="Distributed Scrum Team Help" href="http://3back.com/scrum/agile-distributed-team-training/">scrum distributed</a> teams work?</p>
<p>This is the challenge of business in the 21<sup>st</sup> century: how to work effectively at a distance.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.3back.com/scrum-industry-terms/distributed-agile-teams/feed</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Distributed Agile Development</title>
		<link>http://blog.3back.com/scrum-industry-terms/distributed-agile-development</link>
		<comments>http://blog.3back.com/scrum-industry-terms/distributed-agile-development#comments</comments>
		<pubDate>Mon, 22 Feb 2010 05:00:32 +0000</pubDate>
		<dc:creator>The 3Back Team</dc:creator>
				<category><![CDATA[Scrum Terms]]></category>
		<category><![CDATA[agile distributed teams]]></category>
		<category><![CDATA[distributed agile development]]></category>

		<guid isPermaLink="false">http://blog.3back.com/?p=198</guid>
		<description><![CDATA[ Building and sustaining distributed agile development efforts requires a process that focuses on teams and building up their protocols one at a time.]]></description>
			<content:encoded><![CDATA[<p>Understanding distributed agile development or teams is easier when we consider distribution of agile teams along two dimensions. The first dimension is separation. Separation occurs along time zones, physical distance, language, culture,  The second dimension of a <strong>distributed agile development</strong> effort will be gravity. Building and sustaining distributed agile development efforts requires a process that focuses on teams and building up their protocols one at a time. Tools can help in this distribution process and enable a rapid evolution of team behavior. However, most organizations<a href="http://blog.3back.com/wp-content/uploads/2010/02/Distributed-Agile-Development.gif"><img class="alignright size-full wp-image-200" title="Distributed Agile Development" src="http://blog.3back.com/wp-content/uploads/2010/02/Distributed-Agile-Development.gif" alt="Distributed Agile Scrum Development" width="101" height="87" /></a>simple look at the tool as the means and never find the way. As a result most efforts of distributed agile development are still done very mechanistically which often leads to process fog and low success outcomes. The dimensions of separation and gravity gives us a way to consider things that encourage distance vs. those things that bring the team close together.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.3back.com/scrum-industry-terms/distributed-agile-development/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

