Sprint Backlog is a list of tasks, if mapped to traditional project management theory is the WBS (work breakdown structure), and is typical of the use of task-oriented deliverables decomposition method to get the WBS.
For example, there is a Product backlog entries are:
As a legitimate user of the system, you can log into the system by entering the account number and password.
In order to achieve this requirement, team member identified the task was estimated workload, were the recipients of the task, its results were recorded as:
User stories as a legitimate user of the system, you can log into the system by entering the account number and password.
This table is a developer of thumb based brainstorm with everyone decomposed, which lists the task is to achieve what the user story has to do, in accordance with the principles of simplification, do can not do the task is deleted. Estimated workload is responsible for their own estimates, the total workload of the task should not exceed user story estimation of workload. If the discovery task split the workload is far greater than the sum of the estimated user stories work, you may need to estimate the workload of user stories be revised.
Product owner is responsible for the selection of user stories based on the commercial value of a particular delivery should be included, and the developer is responsible for selecting user stories in an iteration to be achieved based on dependencies between the risk of developing user stories.
Sprint Backlog can use Excel, whiteboard or agile project management tools for maintenance.