The Sprint Backlog

1.  This is a forecast given by the development team as to what functionality will be done in the next increment and how it will be delivered.
2. Contains a set of product backlog items identified for a Sprint and the tasks needed to get those items to done.
3. Tasks are estimated in hours.
4. This is a dynamic document evolving throughout the Sprint.
5. Development team updates the backlog as it works through the plan and understands more the work needed to be done.
6. New work is estimated and added to the backlog by development team.
7. Estimations for remaining work is updated by development team.

9 Tips for Creating a Good Sprint Backlog:

1. Involve every team member in the process.
2. Discuss how every item should be implemented.
3. Have a definition of done.
4. Identify all kinds of tasks.
5. Don't estimate tasks at all. 
6. Don't assign tasks up front
7. Review the sprint commitment. 
8. Don't use too much time.
9. Evolve the Sprint Backlog during the sprint.

Artifacts in the Scrum Framework

List of Artifacts in the Scrum  Framework

1. The Product Backlog
2. The Sprint Backlog
3. The Increment

Product Backlog :

The product backlog is a prioritized features list, containing short descriptions of all functionality desired in the product. When using Scrum, it is not necessary to start a project with a lengthy, upfront effort to document all requirements. Typically, a Scrum team and its product owner begin by writing down everything they can think of easily. This agile backlog is almost always more than enough for a first sprint. The Scrum product backlog is then allowed to grow and change as more is learned about the product and its customers.

Sprint Backlog :

The Sprint Backlog consists of the necessary tasks to realize the final accepted a version of the Selected Product Backlog. The team uses it to synchronize its activities. The tasks turn the Selected Product Backlog into working product functionality.

Increment:

Increment = [all backlog items done in this sprint ] + [increments done in all previous sprints]

An increment must always be in “done” and usable condition.