Scrum Forum

I believe this has been asked couple of time. My comment would be - Dev team is responsible for updating the remaining work and the burndown chart should be generated out of it, so the responsibility lies with Dev team.

Cheers
Sanjay

thx Sanjay Saini.

I'd say the answer depends on which burndown you're talking about. For example:

Sprint Burndown : Development Team
Release Burndown : Product Owner

Hi Derek,

i'am newbie in scrum, then can you explain the difference between both?

While a Sprint the Development Team works on several Product Backlog Items (PBIs) which were picked-up before in the Sprint Planning Meeting from Product Backlog. Inside of a PBI the development Team usually defines some Tasks which are required to finish this PBI, bring it to "done". Now, when the Development Teams finishes a task, then the work-left for the Sprint is smaller than before. With an Sprint Brundown Chart (Example: http://commons.wikimedia.org/wiki/File:Burndown_Chart_of_Agilo_for_Scru…) this can be visualized and make transparent.

On the other side the Product Owner has to observe the whole Product Backlog with all PBIs, and so the work-left, independent of the current Sprint. So how is here the Progress over the project duration? How much work-left for the project? With the help of the Release Burndown Chart can be the left-effort over all Sprints be visualized.