<?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: Full team focusing on a single story VS small surgical teams working on different stories</title>
	<atom:link href="http://scrummasterblog.com/2009/04/full-team-focusing-on-a-single-story-vs-small-surgical-teams-working-on-different-stories/feed/" rel="self" type="application/rss+xml" />
	<link>http://scrummasterblog.com/2009/04/full-team-focusing-on-a-single-story-vs-small-surgical-teams-working-on-different-stories/</link>
	<description>by Mozammel Haque</description>
	<lastBuildDate>Tue, 24 Nov 2009 16:45:43 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Sonali</title>
		<link>http://scrummasterblog.com/2009/04/full-team-focusing-on-a-single-story-vs-small-surgical-teams-working-on-different-stories/comment-page-1/#comment-50</link>
		<dc:creator>Sonali</dc:creator>
		<pubDate>Tue, 24 Nov 2009 16:45:43 +0000</pubDate>
		<guid isPermaLink="false">http://scrummasterblog.com/?p=26#comment-50</guid>
		<description>The team should first finish 1 user story that means that all the design, code &amp; complete testing should be over &amp; then they should pick up the next User story so that whole team is focused on achieving the goal together. But in reality what happens is that most of the teams start picking up parallel user story thinking that they would be able to do it faster but this way of working actually leads to Mini-waterfall within the sprint where Team will finish first the coding of the most/all the US &amp; then start Testing.
The major impact of this is that majority of testing moves towards the end &amp; there is little time left then to fix the faults ending up with the most of the User Stories getting descoped. So, in my opinion the Team should focus on One US at one time or at the maximum 2-3 User Stories.</description>
		<content:encoded><![CDATA[<p>The team should first finish 1 user story that means that all the design, code &amp; complete testing should be over &amp; then they should pick up the next User story so that whole team is focused on achieving the goal together. But in reality what happens is that most of the teams start picking up parallel user story thinking that they would be able to do it faster but this way of working actually leads to Mini-waterfall within the sprint where Team will finish first the coding of the most/all the US &amp; then start Testing.<br />
The major impact of this is that majority of testing moves towards the end &amp; there is little time left then to fix the faults ending up with the most of the User Stories getting descoped. So, in my opinion the Team should focus on One US at one time or at the maximum 2-3 User Stories.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sohan</title>
		<link>http://scrummasterblog.com/2009/04/full-team-focusing-on-a-single-story-vs-small-surgical-teams-working-on-different-stories/comment-page-1/#comment-44</link>
		<dc:creator>Sohan</dc:creator>
		<pubDate>Wed, 21 Oct 2009 01:49:34 +0000</pubDate>
		<guid isPermaLink="false">http://scrummasterblog.com/?p=26#comment-44</guid>
		<description>I am not sure if you want the whole team to work on a single story at all. Can you explain the idea a little? I thought within the sprint, the team is supposed to deliver the sprint goals, however, they should be free to choose their tasks.</description>
		<content:encoded><![CDATA[<p>I am not sure if you want the whole team to work on a single story at all. Can you explain the idea a little? I thought within the sprint, the team is supposed to deliver the sprint goals, however, they should be free to choose their tasks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mozammel</title>
		<link>http://scrummasterblog.com/2009/04/full-team-focusing-on-a-single-story-vs-small-surgical-teams-working-on-different-stories/comment-page-1/#comment-28</link>
		<dc:creator>mozammel</dc:creator>
		<pubDate>Wed, 08 Apr 2009 04:28:00 +0000</pubDate>
		<guid isPermaLink="false">http://scrummasterblog.com/?p=26#comment-28</guid>
		<description>@Mushfiq: Yes I agree that Scrum team aims to achieve the goals together, to be specific, Sprint Goal(s). They do whatever necessary to achieve the sprint goal. There is always a trade off between productivity and stability. Of course if we have full team focusing on single stories, we will produce much stable outcome from our stories, but overall productivity of the team may suffer at the very early stage of our product development. We will certainly consider it as we move from initial release to our engineering team to a more stable maintenance state.</description>
		<content:encoded><![CDATA[<p>@Mushfiq: Yes I agree that Scrum team aims to achieve the goals together, to be specific, Sprint Goal(s). They do whatever necessary to achieve the sprint goal. There is always a trade off between productivity and stability. Of course if we have full team focusing on single stories, we will produce much stable outcome from our stories, but overall productivity of the team may suffer at the very early stage of our product development. We will certainly consider it as we move from initial release to our engineering team to a more stable maintenance state.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mushfiq</title>
		<link>http://scrummasterblog.com/2009/04/full-team-focusing-on-a-single-story-vs-small-surgical-teams-working-on-different-stories/comment-page-1/#comment-27</link>
		<dc:creator>Mushfiq</dc:creator>
		<pubDate>Tue, 07 Apr 2009 17:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://scrummasterblog.com/?p=26#comment-27</guid>
		<description>But I think in standard &#039;Scrum&#039;, the team tries to achieve the goals together. And the full team completes stories one by one. And the full team is responsible to complete the stories. In our case, we failed to follow the standard. The reason may be is our suspicion whether we&#039;ll be able to complete all the stories within Sprint. But I think, we hadn&#039;t tried enough to follow the standard and see what happens. Anyway, I hope we will be able to follow the standard in future Sprints.</description>
		<content:encoded><![CDATA[<p>But I think in standard &#8216;Scrum&#8217;, the team tries to achieve the goals together. And the full team completes stories one by one. And the full team is responsible to complete the stories. In our case, we failed to follow the standard. The reason may be is our suspicion whether we&#8217;ll be able to complete all the stories within Sprint. But I think, we hadn&#8217;t tried enough to follow the standard and see what happens. Anyway, I hope we will be able to follow the standard in future Sprints.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sajid</title>
		<link>http://scrummasterblog.com/2009/04/full-team-focusing-on-a-single-story-vs-small-surgical-teams-working-on-different-stories/comment-page-1/#comment-26</link>
		<dc:creator>Sajid</dc:creator>
		<pubDate>Tue, 07 Apr 2009 10:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://scrummasterblog.com/?p=26#comment-26</guid>
		<description>Nice Post! Nice Pic too ;).  Great to see our experience documented so nicely</description>
		<content:encoded><![CDATA[<p>Nice Post! Nice Pic too <img src='http://scrummasterblog.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> .  Great to see our experience documented so nicely</p>
]]></content:encoded>
	</item>
</channel>
</rss>
