Sprint burn-down
Sprint burn-down is an outcome of a sprint. As tasks get completed the burn-down chart shows how much work is still to be completed and whether the team is on track or not. If the team is not on track to deliver the sprint as planned, then it is a message to the Scrum Master to find out any obstacles the team might have.
This often involves the Product Owner as the obstacles might be user stories that require additional information or decisions. A Product Owner should try to solve these obstacles as quickly as possible and later reflect if and how the issues could have been avoided with better prioritizing and planning prior to the sprint.
Summary
Creating a sprint backlog is a complex process spanning many stakeholders and activities. In order to create a good sprint backlog that delivers maximum value to the users with reasonable effort from the developers. The Scrum team needs to constantly work on improving their velocity and keeping their backlog estimated and relevant to the product vision.
For this Scrum provides many different tools like user stories, prioritizing meeting, planning meeting and velocity tracking using the burn-down chart.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: