The team should have an idea of how they would be able to manage themselves during a sprint. It is hard for some team members to recall sometimes how long they should work on a certain task. There are some who cannot help but become confused with the tasks that are assigned to them.
This is always something that the whole team can work on. The more that the team can see the tasks that they have to do plus the time frame for each task, the better the process will flow. Better management can lead to the completion of the various tasks that the team has to accomplish given a certain period of time.
The sprint backlog consists of the different tasks that the Scrum team would need to complete during the Scrum sprint. Knowing this, the answer to this question is B. There are different user stories that the rest of the team will choose. Their main goal is to complete the user stories. The user stories will determine the type of tasks that the Scrum team would have to do.
These are usually tasks that they need to improve further so that if they would encounter the same situations in the future, they would know what to do. Take note that all of the user stories will usually be discussed first to provide further information to the rest of the team.
The main purpose of a Sprint Backlog is - for the team to manage themselves during the Sprint.
Basically, a Sprint Backlog is a list of tasks identified by the Scrum team and these tasks have to be completed during the Scrum sprint. Here, the team selects some product backlog items mainly in the user stories form. Afterward, the necessary tasks are identified to complete each user story by the team.