<?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: The Task Burn Down Trap: everything finished, nothing done</title>
	<atom:link href="http://blog.xebia.com/2008/09/19/the-task-burn-down-trap-everything-finished-nothing-done/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com/2008/09/19/the-task-burn-down-trap-everything-finished-nothing-done/</link>
	<description>Software development done right!</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:41:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Erik Pragt</title>
		<link>http://blog.xebia.com/2008/09/19/the-task-burn-down-trap-everything-finished-nothing-done/#comment-53803</link>
		<dc:creator>Erik Pragt</dc:creator>
		<pubDate>Fri, 19 Sep 2008 11:56:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=756#comment-53803</guid>
		<description>@1: Well, if you make your User Stories small enough (which you should) you already have a trend. Why do you want to have two trends?

@2: I know. Just giving you something to do for the weekend ;). (And a small reference could be made to the next iteration, unless you want to write a blog: &#039;everything finished, nothing to do next sprint&#039; ;)</description>
		<content:encoded><![CDATA[<p>@1: Well, if you make your User Stories small enough (which you should) you already have a trend. Why do you want to have two trends?</p>
<p>@2: I know. Just giving you something to do for the weekend <img src='http://blog.xebia.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> . (And a small reference could be made to the next iteration, unless you want to write a blog: &#8216;everything finished, nothing to do next sprint&#8217; <img src='http://blog.xebia.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serge Beaumont</title>
		<link>http://blog.xebia.com/2008/09/19/the-task-burn-down-trap-everything-finished-nothing-done/#comment-53802</link>
		<dc:creator>Serge Beaumont</dc:creator>
		<pubDate>Fri, 19 Sep 2008 11:51:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=756#comment-53802</guid>
		<description>Erik,

@1: What the task burn down adds is *trend* information, while a task board only gives you a snapshot of the current situation. So there&#039;s definitely something it adds.

@2: You&#039;re absolutely right to note that working on the next Sprint is worth a blog post on its own. That&#039;s why it&#039;s not in this one. :-)</description>
		<content:encoded><![CDATA[<p>Erik,</p>
<p>@1: What the task burn down adds is *trend* information, while a task board only gives you a snapshot of the current situation. So there&#8217;s definitely something it adds.</p>
<p>@2: You&#8217;re absolutely right to note that working on the next Sprint is worth a blog post on its own. That&#8217;s why it&#8217;s not in this one. <img src='http://blog.xebia.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Pragt</title>
		<link>http://blog.xebia.com/2008/09/19/the-task-burn-down-trap-everything-finished-nothing-done/#comment-53801</link>
		<dc:creator>Erik Pragt</dc:creator>
		<pubDate>Fri, 19 Sep 2008 11:44:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=756#comment-53801</guid>
		<description>Hi Serge,

Interesting blog. However, 2 remarks:

1: throw away the task burn down! It adds nothing, and only produces waste (we don&#039;t want that, do we?). This information is already available on the task board, so don&#039;t add it again.

2: I think you focus a little bit to much on the current sprint, while not touching the NEXT sprint (sorry for the uppercase). I think that&#039;s worth a blog on it&#039;s own, but if you have an hour to spare, check out this movie: http://www.infoq.com/presentations/prioritizing-your-product-backlog-mike-cohn</description>
		<content:encoded><![CDATA[<p>Hi Serge,</p>
<p>Interesting blog. However, 2 remarks:</p>
<p>1: throw away the task burn down! It adds nothing, and only produces waste (we don&#8217;t want that, do we?). This information is already available on the task board, so don&#8217;t add it again.</p>
<p>2: I think you focus a little bit to much on the current sprint, while not touching the NEXT sprint (sorry for the uppercase). I think that&#8217;s worth a blog on it&#8217;s own, but if you have an hour to spare, check out this movie: <a href="http://www.infoq.com/presentations/prioritizing-your-product-backlog-mike-cohn" rel="nofollow">http://www.infoq.com/presentations/prioritizing-your-product-backlog-mike-cohn</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  blog.xebia.com/2008/09/19/the-task-burn-down-trap-everything-finished-nothing-done/feed/ ) in 0.51530 seconds, on Feb 9th, 2012 at 9:02 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on Feb 9th, 2012 at 10:02 pm UTC -->
