Re: [scrumdevelopment] Understanding the Scrum Burndown Chart
- I am also on the same page...But is there any other mechanisms in the way to get this clues (from the deviations)...In my view it atleast provides some indicators when comapred as expected vs. actual..From: Steve Ropa <theropas@...>
Sent: Wednesday, 25 January 2012 4:13 AM
Subject: RE: [scrumdevelopment] Understanding the Scrum Burndown ChartYeah, we had the same experience.I am with you on the “no longer a fan” bandwagon as well.From: email@example.com [mailto:firstname.lastname@example.org] On Behalf Of Michael James
Sent: Tuesday, January 24, 2012 3:20 PM
Subject: Re: [scrumdevelopment] Understanding the Scrum Burndown ChartAdding to that, there wasn't any "ideal line" when the Sprint Burndown was first described in writing, it seems to have been added by tools vendors. It's not prescribed by Scrum, and certainly not a desirable enhancement. I argued against including it in the tool I was involved with, but customers demanded it because the competitors had it....--mj (no longer a fan of the Sprint Burndown anyway)On Jan 24, 2012, at 1:46 PM, Steve Ropa wrote:I’ve been telling people to ignore the “ideal line” for years. Sadly, that usually irritates some of the PM’s I talk to.+1. Let's not pretend creative work is as predictable as manufacturing.
On Jan 24, 2012, at 11:28 AM, "woynam" <woyna@...> wrote:
The diagrams demonstrate one of the biggest pitfalls in using burndowns: displaying the "ideal" line.
I've seen too many teams try to game the system to achieve the "perfect" burn down. My recommendation is to *not* display the "ideal" line. If you're team is tracking ideally, I'm guessing that their lying.
--- In email@example.com, "ginitram" <ginitram@...> wrote:
> The Methods & Tools newsletter has just released in its html archive section the article "Understanding the Scrum Burndown Chart" by Dusan Kocurek. The Scrum Burndown chart is very simple. It is easy to explain, easy to understand. But this metric also put in evidence some pitfalls observed in many agile workshops and adoptions. This article discuss them.