<?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 Scrum on Larger Projects: &quot;Scrum of Scrums&quot;</title>
	<atom:link href="http://www.allaboutagile.com/using-scrum-on-larger-projects-scrum-of-scrums/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allaboutagile.com/using-scrum-on-larger-projects-scrum-of-scrums/</link>
	<description>Agile Development Made Easy!</description>
	<lastBuildDate>Sun, 19 May 2013 08:16:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Rod Clar</title>
		<link>http://www.allaboutagile.com/using-scrum-on-larger-projects-scrum-of-scrums/#comment-540</link>
		<dc:creator>Rod Clar</dc:creator>
		<pubDate>Wed, 10 Jun 2009 12:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/using-scrum-on-larger-projects-scrum-of-scrums/#comment-540</guid>
		<description><![CDATA[Annother approach to handling the communiation and contention between teams is to use retrospectives to identify specific areas where the larger number of teams was less effective than a small team.  For instance code contention, shared resources or cross-team requirements.  In cases like this create more SoS teams with different local representatives at those scrum meetings.]]></description>
		<content:encoded><![CDATA[<p>Annother approach to handling the communiation and contention between teams is to use retrospectives to identify specific areas where the larger number of teams was less effective than a small team.  For instance code contention, shared resources or cross-team requirements.  In cases like this create more SoS teams with different local representatives at those scrum meetings.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PuristProductManagement</title>
		<link>http://www.allaboutagile.com/using-scrum-on-larger-projects-scrum-of-scrums/#comment-539</link>
		<dc:creator>PuristProductManagement</dc:creator>
		<pubDate>Wed, 10 Jun 2009 08:30:19 +0000</pubDate>
		<guid isPermaLink="false">http://allaboutagile.com/uncategorized/using-scrum-on-larger-projects-scrum-of-scrums/#comment-539</guid>
		<description><![CDATA[Yes scrum of scrums works well and certainly helps co-ordinate communication across multiple scrum teams. In my experiance an important factor in success of multi-scrum large scale projects is dis-associating the work streams as far as possible, and having strong product and project management functions that can mitigate interdependencies effectivly. This is tough, and requires protracted elaboration periods, but from experiance the time spent earlier saves weeks later. Scrum of Scrums certainly helps this!]]></description>
		<content:encoded><![CDATA[<p>Yes scrum of scrums works well and certainly helps co-ordinate communication across multiple scrum teams. In my experiance an important factor in success of multi-scrum large scale projects is dis-associating the work streams as far as possible, and having strong product and project management functions that can mitigate interdependencies effectivly. This is tough, and requires protracted elaboration periods, but from experiance the time spent earlier saves weeks later. Scrum of Scrums certainly helps this!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
