Skip to main content

Release BurnDown

Last post 05:13 pm July 26, 2014 by nikos batsios
4 replies
12:43 am July 8, 2014

Hi All
Is Release Burndown Chart acceptable concept in Scrum? Burndown by definition should signify the amount of Work reamining..And generally we cannot have a Release planning covering all the Sprints . Sprint Planning takes place at the beginning of the Sprint only.So what is Release Burndown suppossed to contain or signify?

Thanks
---Abhijit


05:20 am July 8, 2014

It's an acceptable concept but it is no longer part of the framework. See:

https://www.scrum.org/About/All-Articles/articleType/ArticleView/articl…


05:35 am July 8, 2014

Thanks Ian.. Got that...


08:18 pm July 8, 2014

So, if it is not part anymore, how should a question on the Assessment be treated? I mean, if it is part of the question itself?


05:13 pm July 26, 2014

you can refer to "scrum - a pocket guide" as well...


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.