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.