<?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: Burn-up and burn-down charts</title>
	<atom:link href="http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/feed/" rel="self" type="application/rss+xml" />
	<link>http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/</link>
	<description>Mostly about the management of software development</description>
	<lastBuildDate>Wed, 27 Jan 2010 09:48:25 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rob Myers</title>
		<link>http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/comment-page-1/#comment-33959</link>
		<dc:creator>Rob Myers</dc:creator>
		<pubDate>Tue, 18 Aug 2009 01:40:23 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-33959</guid>
		<description>Even though burn-downs are simpler, burn-ups are pretty simple, and the motivational &quot;goal&quot; is to watch the lines meet at the end of the iteration (or release, if a release burn-up).  In fact, though there is a motivational factor here, this graph is more significant as a reality-check and planning tool.  The lines at the end WILL meet.  There is no way around it, unless you know how to stop time (and you don&#039;t).  That&#039;s what I like most about the burn-up:  It readily reveals scope-creep (which could get hidden by a burn-down) and it shows the opposite, too, when scope is cut in order to meet the deadline.  Burn-downs show scope reductions as some strange miraculous period of performance.  &quot;Why can&#039;t your team work like that all the time?&quot;

Let it be an information-radiator, not a motivation-radiator, and it will motivate.  Let it be a reflection of what&#039;s really happening, rather than fudging the numbers.

Nice graphic, BTW.  Can I borrow your burn-down for Agile 2009?  It shows up as one of the first in a Google Images search for &quot;chart down&quot; or whatever I asked for...  ;-)</description>
		<content:encoded><![CDATA[<p>Even though burn-downs are simpler, burn-ups are pretty simple, and the motivational &#8220;goal&#8221; is to watch the lines meet at the end of the iteration (or release, if a release burn-up).  In fact, though there is a motivational factor here, this graph is more significant as a reality-check and planning tool.  The lines at the end WILL meet.  There is no way around it, unless you know how to stop time (and you don&#8217;t).  That&#8217;s what I like most about the burn-up:  It readily reveals scope-creep (which could get hidden by a burn-down) and it shows the opposite, too, when scope is cut in order to meet the deadline.  Burn-downs show scope reductions as some strange miraculous period of performance.  &#8220;Why can&#8217;t your team work like that all the time?&#8221;</p>
<p>Let it be an information-radiator, not a motivation-radiator, and it will motivate.  Let it be a reflection of what&#8217;s really happening, rather than fudging the numbers.</p>
<p>Nice graphic, BTW.  Can I borrow your burn-down for Agile 2009?  It shows up as one of the first in a Google Images search for &#8220;chart down&#8221; or whatever I asked for&#8230;  <img src='http://niksilver.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jesse</title>
		<link>http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/comment-page-1/#comment-33958</link>
		<dc:creator>Jesse</dc:creator>
		<pubDate>Sun, 26 Jul 2009 22:29:04 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-33958</guid>
		<description>I&#039;m surprised at how many people use burn down charts over burn up charts which are way more informative. It&#039;s hard to find burn up chart software. I&#039;m using NXS-7&#039;s Task Analytics http://task-analytics.com burn up charts. It&#039;s been pretty good.</description>
		<content:encoded><![CDATA[<p>I&#8217;m surprised at how many people use burn down charts over burn up charts which are way more informative. It&#8217;s hard to find burn up chart software. I&#8217;m using NXS-7&#8217;s Task Analytics <a href="http://task-analytics.com" rel="nofollow">http://task-analytics.com</a> burn up charts. It&#8217;s been pretty good.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marcin</title>
		<link>http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/comment-page-1/#comment-33957</link>
		<dc:creator>Marcin</dc:creator>
		<pubDate>Tue, 21 Jul 2009 14:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-33957</guid>
		<description>I hope you don&#039;t mind we&#039;re referencing this article on Banana Scrum site http://www.bananascrum.com/news/2009/07/16/track-the-progress-of-your-team-with-burnup-chart/

Thanks,</description>
		<content:encoded><![CDATA[<p>I hope you don&#8217;t mind we&#8217;re referencing this article on Banana Scrum site <a href="http://www.bananascrum.com/news/2009/07/16/track-the-progress-of-your-team-with-burnup-chart/" rel="nofollow">http://www.bananascrum.com/news/2009/07/16/track-the-progress-of-your-team-with-burnup-chart/</a></p>
<p>Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nik</title>
		<link>http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/comment-page-1/#comment-33948</link>
		<dc:creator>Nik</dc:creator>
		<pubDate>Fri, 29 May 2009 17:06:08 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-33948</guid>
		<description>Burn up charts aren&#039;t just to track feature creep, but also changes in estimates. Though I agree about the motivational benefits of a line cruising to zero.</description>
		<content:encoded><![CDATA[<p>Burn up charts aren&#8217;t just to track feature creep, but also changes in estimates. Though I agree about the motivational benefits of a line cruising to zero.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephan Schmidt</title>
		<link>http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/comment-page-1/#comment-33946</link>
		<dc:creator>Stephan Schmidt</dc:creator>
		<pubDate>Fri, 29 May 2009 11:47:45 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-33946</guid>
		<description>I find burn down charts excellent as a motivation tool (as a side effect). Burn up charts are if anything frustrating.

As a ScrumMaster I&#039;d say just keep feature creep out.

Cheers
Stephan
http://twitter.com/codemonkeyism</description>
		<content:encoded><![CDATA[<p>I find burn down charts excellent as a motivation tool (as a side effect). Burn up charts are if anything frustrating.</p>
<p>As a ScrumMaster I&#8217;d say just keep feature creep out.</p>
<p>Cheers<br />
Stephan<br />
<a href="http://twitter.com/codemonkeyism" rel="nofollow">http://twitter.com/codemonkeyism</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quando o ócio não é culpa do time! &#171; Paulo R. A. Sales Blog</title>
		<link>http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/comment-page-1/#comment-33936</link>
		<dc:creator>Quando o ócio não é culpa do time! &#171; Paulo R. A. Sales Blog</dc:creator>
		<pubDate>Fri, 06 Feb 2009 16:11:59 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-33936</guid>
		<description>[...] Tem um artigo bem direto quanto a utilização e alguns benefícios de utilizar o burn-up chart: Burn-up e Burn-Down. [...]</description>
		<content:encoded><![CDATA[<p>[...] Tem um artigo bem direto quanto a utilização e alguns benefícios de utilizar o burn-up chart: Burn-up e Burn-Down. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
