Comments on: Burn-up and burn-down charts http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/ Mostly about the management of software development Thu, 10 May 2012 08:56:13 +0000 hourly 1 http://wordpress.com/ By: Claus http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-290 Wed, 14 Sep 2011 09:19:59 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-290 Patrick: With this information you’re actually able to calculate Earned Value for the ongoing project as well. This is very useful for progress reporting as well.

]]> By: patrick sarfati http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-289 Thu, 21 Jul 2011 09:14:22 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-289 Concerning my experience, I am coaching projects since 1995 (from small to very large project, from start-up organizations to large multinational companies)
Burndown chart is a very smart add from Scrum Methodology: it allows to track the ETC

ETC is something very heavy to follow-up/ track in the standard Project Management Method, but with the Burndown chart, you get it for free , this is just awesome!

Moreover, the idea itself of burdndown chart means focusing on a sprint target and try to reach it. Do not forget in Scrum, you are agile, but the scope of the sprint is frozen. As I often say it in my trainings, there is a difference between Agile development and chaotic development: the limit of agility in scrum is to have a fix scope for each sprint, else the project could permanently change it scope, to deliver…nothing, circling and not moving forward

So What I mean is that it is very important to focus on the idea to deliver in time the committed content for iteration, and for that burndown chart are king’s

Having good BurnUp does not show you deliver the expected scope in time, just show you produce at a good rhythm, but the focus of scrum is not to make a software factory where only production is encourage, but to produce the right thing!
By the Way, working with ETC provides you a higher Project Management Maturity rather than only counting the time spent or the produced story points or man days (refer to PMI or CMMI)

Patrick Sarfati
soft-method.com

]]> By: stevenlamb http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-288 Mon, 03 Jan 2011 02:08:51 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-288 I tried NXS-7 Task Analytics http://task-analytics.com and it was pretty basic. It’s ok for Micky Mouse projects but for something more sophisticated try atlassian.com

]]> By: Rob Myers http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-287 Tue, 18 Aug 2009 01:40:23 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-287 Even though burn-downs are simpler, burn-ups are pretty simple, and the motivational “goal” 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’t). That’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. “Why can’t your team work like that all the time?”

Let it be an information-radiator, not a motivation-radiator, and it will motivate. Let it be a reflection of what’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 “chart down” or whatever I asked for… ;-)

]]> By: Jesse http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-286 Sun, 26 Jul 2009 22:29:04 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-286 I’m surprised at how many people use burn down charts over burn up charts which are way more informative. It’s hard to find burn up chart software. I’m using NXS-7′s Task Analytics http://task-analytics.com burn up charts. It’s been pretty good.

]]> By: Marcin http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-285 Tue, 21 Jul 2009 14:41:33 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-285 I hope you don’t mind we’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,

]]> By: Nik http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-284 Fri, 29 May 2009 17:06:08 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-284 Burn up charts aren’t just to track feature creep, but also changes in estimates. Though I agree about the motivational benefits of a line cruising to zero.

]]> By: Stephan Schmidt http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-283 Fri, 29 May 2009 11:47:45 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-283 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’d say just keep feature creep out.

Cheers
Stephan
http://twitter.com/codemonkeyism

]]> By: Quando o ócio não é culpa do time! « Paulo R. A. Sales Blog http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-282 Fri, 06 Feb 2009 16:11:59 +0000 http://niksilver.com/2008/01/19/burn-up-and-burn-down-charts/#comment-282 [...] Tem um artigo bem direto quanto a utilização e alguns benefícios de utilizar o burn-up chart: Burn-up e Burn-Down. [...]

]]>