<?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: Prioritising stories within a sprint?</title>
	<atom:link href="http://blog.valtech.co.uk/scrum/prioritising-stories-within-a-sprint/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.valtech.co.uk/scrum/prioritising-stories-within-a-sprint/</link>
	<description>Aggregated works of Valtech UK consultants</description>
	<lastBuildDate>Sun, 18 Dec 2011 21:16:58 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: David Draper</title>
		<link>http://blog.valtech.co.uk/scrum/prioritising-stories-within-a-sprint/comment-page-1/#comment-131</link>
		<dc:creator>David Draper</dc:creator>
		<pubDate>Fri, 19 Feb 2010 09:48:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.agiledesign.co.uk/scrum/prioritising-stories-within-a-sprint/#comment-131</guid>
		<description>I see a risk of us violently agreeing :)

First of all, &quot;Priority:Must&quot; as you put it is not helpful, for me prioritisation is simply this one first. This is a distinct conversation from scope i.e. must vs. won&#039;t.

As with any guideline there are exceptions - I don&#039;t propose for a moment that we replace common sense with prioritisation.

The focus of the post was in response to common advice given to Scrum teams. Limiting WiP (in terms of stories) in this context is achieved by the sprint. The question posed was &quot;should we prioritise stories within a sprint?&quot;. My response was yes, this could be combined with task level WiP limits though this is not common.</description>
		<content:encoded><![CDATA[<p>I see a risk of us violently agreeing <img src='http://blog.valtech.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>First of all, &#8220;Priority:Must&#8221; as you put it is not helpful, for me prioritisation is simply this one first. This is a distinct conversation from scope i.e. must vs. won&#8217;t.</p>
<p>As with any guideline there are exceptions &#8211; I don&#8217;t propose for a moment that we replace common sense with prioritisation.</p>
<p>The focus of the post was in response to common advice given to Scrum teams. Limiting WiP (in terms of stories) in this context is achieved by the sprint. The question posed was &#8220;should we prioritise stories within a sprint?&#8221;. My response was yes, this could be combined with task level WiP limits though this is not common.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ruud Rietveld</title>
		<link>http://blog.valtech.co.uk/scrum/prioritising-stories-within-a-sprint/comment-page-1/#comment-127</link>
		<dc:creator>Ruud Rietveld</dc:creator>
		<pubDate>Thu, 18 Feb 2010 12:06:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.agiledesign.co.uk/scrum/prioritising-stories-within-a-sprint/#comment-127</guid>
		<description>You say you recommend using prioritisation in a sprint. I think I want to achieve the same result, but I would not call it prioritisation.
You say prioritisation helps because:
    * The team is challenged to find ways to move stories to Done faster
    * The team is encouraged to collaborate and help each other out in favour of picking new tasks
    * We bind people to tasks late, prioritisation helps them select tasks according to team need rather than specialisation
    * Where a sprint commitment is missed we loose 1 story rather than a bit from each story.

I do not see how prioritisation helps in that. You only need to say that you want to limit WiP. &quot;Priority: Must&quot; has never incentised people to work harder.
Prioritisation can also work against you: If there is time left at the end of the sprint for only the smaller bottom unstarted story, and not time enough for a higher-up unstarted story, you have to start the higher-up one, and will end the sprint with two unfinished stories instead of one.</description>
		<content:encoded><![CDATA[<p>You say you recommend using prioritisation in a sprint. I think I want to achieve the same result, but I would not call it prioritisation.<br />
You say prioritisation helps because:<br />
    * The team is challenged to find ways to move stories to Done faster<br />
    * The team is encouraged to collaborate and help each other out in favour of picking new tasks<br />
    * We bind people to tasks late, prioritisation helps them select tasks according to team need rather than specialisation<br />
    * Where a sprint commitment is missed we loose 1 story rather than a bit from each story.</p>
<p>I do not see how prioritisation helps in that. You only need to say that you want to limit WiP. &#8220;Priority: Must&#8221; has never incentised people to work harder.<br />
Prioritisation can also work against you: If there is time left at the end of the sprint for only the smaller bottom unstarted story, and not time enough for a higher-up unstarted story, you have to start the higher-up one, and will end the sprint with two unfinished stories instead of one.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

