Forums

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. If you have left the first and last name fields blank on your member profile, your email address will be displayed instead.

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.

Who is responsable by the burndownchart ?
Last Post 09 Nov 2013 02:24 AM by Christian Nicoll. 5 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages Informative
rhurick silva
New Member
New Member
Posts:8
rhurick silva

--
16 Oct 2013 08:55 PM
    hello guys i have a doubt, whto is responsable by the burndownchart: Scrum Master, Product Owner or Dev Team ?
    Sanjay Saini
    Basic Member
    Basic Member
    Posts:139
    Sanjay Saini

    --
    16 Oct 2013 10:00 PM

    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
    rhurick silva
    New Member
    New Member
    Posts:8
    rhurick silva

    --
    17 Oct 2013 10:45 AM
    thx Sanjay Saini.
    Derek Davidson
    New Member
    New Member
    Posts:9
    Derek Davidson

    --
    04 Nov 2013 10:25 AM
    I'd say the answer depends on which burndown you're talking about. For example:

    Sprint Burndown : Development Team
    Release Burndown : Product Owner
    rhurick silva
    New Member
    New Member
    Posts:8
    rhurick silva

    --
    06 Nov 2013 06:53 AM
    Hi Derek,

    i'am newbie in scrum, then can you explain the difference between both?
    Christian Nicoll
    New Member
    New Member
    Posts:9
    Christian Nicoll

    --
    09 Nov 2013 02:24 AM
    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_Scrum.png) 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.
    You are not authorized to post a reply.


    Feedback