!!! Overview
[{$pagename}] ([Iteration Backlog]) is the prioritize [user stories|User Story] or often [Agile Tasks] chosen by the [Scrum Team] to be taken to the [Definition of Done] during the [Iteration][{$pagename}] is the subset of the [Product Backlog]. Each [Iteration], [Scrum Team] picks the [Agile Tasks] from [Product Backlog] on top of its stack, the number of [Agile Tasks] is determined by the [Product Owner] for an [Iteration] is based on the average [velocity] of a [Scrum Team].

Those [user stories|User Story] which moved to [Iteration] is owned by [Scrum Team] as the team is __committed__ [Iteration].

[{$pagename}] is dynamic in nature, each [sprint] the above scenario is repeated. Good practice is to keep the [{$pagename}] as static as possible during a [Iteration].During each [Iteration Planning] session, the team returns back to [Product Backlog] to pick recently prioritized [user stories|User Story] for the [Iteration].

* [{$pagename}] is a subset of [Product Backlog]
* [{$pagename}] is an output of a sprint planning meeting.

In [{$pagename}], [Scrum Team] works on how the user stories would be implemented in a sprint by dividing it further into tasks and estimating it.

Assuming Product Backlog has stories: 1, 2, 3, 4 , 5 and 6. The team decides to do stories 1,2 and 4. As during [Iteration Planning] the [Scrum Team] realized that there still some question which is not answered well by the [Product Owner], so they decided not to include the [User Story] no: 3 and jump to user story no:4, which was defined well.[{$pagename}] is owned by the [Development Team] and contains what is to be taken to the [Definition of Done] during the [Iteration] in each [Iteration Planning] the existing [{$pagename}] is replaced with a new [{$pagename}]

!! More Information
There might be more information for this subject on one of the following:
[{ReferringPagesPlugin before='*' after='\n' }]