<?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: Forming, Storming, Norming, and Swarming – The Tuckman Model for Scrum</title>
	<atom:link href="http://www.rallydev.com/agileblog/2009/10/forming-storming-norming-and-swarming-%E2%80%93-the-tuckman-model-for-scrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.rallydev.com/agileblog/2009/10/forming-storming-norming-and-swarming-%e2%80%93-the-tuckman-model-for-scrum/</link>
	<description>Adopt, Scale and Succeed with Agile Development</description>
	<lastBuildDate>Tue, 10 Jan 2012 03:30:50 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>By: Karen Favazza Spencer</title>
		<link>http://www.rallydev.com/agileblog/2009/10/forming-storming-norming-and-swarming-%e2%80%93-the-tuckman-model-for-scrum/#comment-9653</link>
		<dc:creator>Karen Favazza Spencer</dc:creator>
		<pubDate>Tue, 08 Mar 2011 22:12:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3673#comment-9653</guid>
		<description>Love it! Although I&#039;ve experienced it in short bursts on occasion, I&#039;ve yet to actually see swarming as a disciplined routine Modus Operandi, but I have faith. 

Still let me offer this. It doesn&#039;t have to be the entire team on just one story, they could be swarming on two stories at the top of the list. It is based on tasks to go around. But those very tasks are different, too. Tasks that are typically neglected in waterfall that should be included in the implementation of most Agile User Stories include programming automated tests. This should be done in concert with the actual coding and involves testers before programmers. It&#039;s a whole other mindset around the definition of done that encourages an holistic rather than hierarchal approach, in addition to blurring the distinction between testers and programmers.</description>
		<content:encoded><![CDATA[<p>Love it! Although I&#8217;ve experienced it in short bursts on occasion, I&#8217;ve yet to actually see swarming as a disciplined routine Modus Operandi, but I have faith. </p>
<p>Still let me offer this. It doesn&#8217;t have to be the entire team on just one story, they could be swarming on two stories at the top of the list. It is based on tasks to go around. But those very tasks are different, too. Tasks that are typically neglected in waterfall that should be included in the implementation of most Agile User Stories include programming automated tests. This should be done in concert with the actual coding and involves testers before programmers. It&#8217;s a whole other mindset around the definition of done that encourages an holistic rather than hierarchal approach, in addition to blurring the distinction between testers and programmers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Atlas</title>
		<link>http://www.rallydev.com/agileblog/2009/10/forming-storming-norming-and-swarming-%e2%80%93-the-tuckman-model-for-scrum/#comment-4612</link>
		<dc:creator>Alan Atlas</dc:creator>
		<pubDate>Fri, 30 Oct 2009 15:51:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3673#comment-4612</guid>
		<description>Hi Tony,
That is the perfect question to ask. The answer is that there are a few different ways of working that support this. One thing is to put some discipline into breaking work down into small tasks. It&#039;s possible to work on changes to two methods in the same class at the same time. You just need to be working closely together.

Two people working on two tasks will have an easier time coordinating their check-ins than two people trying to work on one task. And there&#039;s always the natural division between writing tests and writing code. If your team gets the idea of swarming and likes it, they will find ways to make it happen better and better over time.

alan</description>
		<content:encoded><![CDATA[<p>Hi Tony,<br />
That is the perfect question to ask. The answer is that there are a few different ways of working that support this. One thing is to put some discipline into breaking work down into small tasks. It&#8217;s possible to work on changes to two methods in the same class at the same time. You just need to be working closely together.</p>
<p>Two people working on two tasks will have an easier time coordinating their check-ins than two people trying to work on one task. And there&#8217;s always the natural division between writing tests and writing code. If your team gets the idea of swarming and likes it, they will find ways to make it happen better and better over time.</p>
<p>alan</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tweets that mention Forming, Storming, Norming, and Swarming – The Tuckman Model for Scrum &#124; Agile Blog: Scaling Software Agility -- Topsy.com</title>
		<link>http://www.rallydev.com/agileblog/2009/10/forming-storming-norming-and-swarming-%e2%80%93-the-tuckman-model-for-scrum/#comment-4596</link>
		<dc:creator>Tweets that mention Forming, Storming, Norming, and Swarming – The Tuckman Model for Scrum &#124; Agile Blog: Scaling Software Agility -- Topsy.com</dc:creator>
		<pubDate>Fri, 30 Oct 2009 06:42:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3673#comment-4596</guid>
		<description>[...] This post was mentioned on Twitter by Rally Software, espejocosmico, Agile Blog, Willy Mejia, Paul Jackson and others. Paul Jackson said: RT @agiledeveloper Forming, Storming, Norming, and Swarming – The Tuckman Model for Scrum http://bit.ly/4CYgxF #agile [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Rally Software, espejocosmico, Agile Blog, Willy Mejia, Paul Jackson and others. Paul Jackson said: RT @agiledeveloper Forming, Storming, Norming, and Swarming – The Tuckman Model for Scrum <a href="http://bit.ly/4CYgxF" rel="nofollow">http://bit.ly/4CYgxF</a> #agile [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lev Ayzner</title>
		<link>http://www.rallydev.com/agileblog/2009/10/forming-storming-norming-and-swarming-%e2%80%93-the-tuckman-model-for-scrum/#comment-4595</link>
		<dc:creator>Lev Ayzner</dc:creator>
		<pubDate>Fri, 30 Oct 2009 06:37:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3673#comment-4595</guid>
		<description>I&#039;d re-phrase Tony&#039;s question as asking to add a definition of &quot;Working&quot; to the model that defines Forming, Storming, Norming, and Performing. And that is what the teams achieves in the Norming stage. As often, the only right answer is &quot;It depends...&quot;

Thanks, 

LA</description>
		<content:encoded><![CDATA[<p>I&#8217;d re-phrase Tony&#8217;s question as asking to add a definition of &#8220;Working&#8221; to the model that defines Forming, Storming, Norming, and Performing. And that is what the teams achieves in the Norming stage. As often, the only right answer is &#8220;It depends&#8230;&#8221;</p>
<p>Thanks, </p>
<p>LA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony Yunnie</title>
		<link>http://www.rallydev.com/agileblog/2009/10/forming-storming-norming-and-swarming-%e2%80%93-the-tuckman-model-for-scrum/#comment-4587</link>
		<dc:creator>Tony Yunnie</dc:creator>
		<pubDate>Thu, 29 Oct 2009 19:18:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.rallydev.com/agileblog/?p=3673#comment-4587</guid>
		<description>Hi Alan, thanks for the blog, I like the swarming idea, however I&#039;m battling to get my head around how a team all work on a PBI - how do a number of developers work on the same item - the same piece of code? We aren&#039;;t talking pair programming. Does a PBI get broken into multiple tasks and then each person or pair works on one task?

Thanks - TY.</description>
		<content:encoded><![CDATA[<p>Hi Alan, thanks for the blog, I like the swarming idea, however I&#8217;m battling to get my head around how a team all work on a PBI &#8211; how do a number of developers work on the same item &#8211; the same piece of code? We aren&#8217;;t talking pair programming. Does a PBI get broken into multiple tasks and then each person or pair works on one task?</p>
<p>Thanks &#8211; TY.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

