The Sprint Backlog is one of the three Scrum Artifacts. It is an output of sprint planning and is created by the Development Team. The artifact is used to forecast the functionality of the next product increment and represents the committed work for the sprint.
The Sprint Backlog should contain the Product Backlog selected for the current sprint and the work needed to deliver a “done” product increment. In other words, it contains the plan for completing the product increment and aims to achieve the Sprint Goal.
The Sprint Backlog emerges during the Sprint as work progresses and the Development Team understands more about what is needed. Items are added to the Sprint Backlog by the Development Team as new work is required. Conversely, items that are found to be unnecessary during the Sprint are removed from the Sprint Backlog.
The Sprint Backlog belongs solely to the Development Team. This means that it is updated by the Development Team. The artifact, however, should be highly visible to everyone and kept up to date by the Development Team to represent a real-time picture of the work.