Explain the use of burn-up and burn-down charts in a Scrum Project?
Burnup and Burndown charts are not part of core Scrum, but they provide the Development Team and the Product Owner a way to track the progress at Sprint Level and overall Project Progress. Burndown helps to track work remaining against Sprint time and burnup helps to track work done against release time. Sprint level tracking is done by the Development team and Project level tracking is done by the Product owner. Both burnup and burndown can be used at Sprint level and Project level. Sprint level (burndown/burnup) should ideally be updated by Development Team as and when they complete an item during the Sprint or at least once in a day. Release level (burndown/burnup) should be updated by the Product Owner at the end of every Sprint before going to Sprint Review. This helps the Product Owner to make scope vs time trade-off decisions.
**Hit the link to send your queries to us about this question, our experts will reach out to you at the earliest!