Sprint Backlog
A plan by and for the Developers, composed of the Sprint Goal, the selected Product Backlog items, and the plan to deliver the Increment.
What it means
The Sprint Backlog is one of the three Scrum artifacts. It is a highly visible, real-time picture of the work the Developers plan to accomplish during the Sprint to achieve the Sprint Goal.
It is owned exclusively by the Developers. They can add, remove, or re-plan items throughout the Sprint as they learn more, as long as the Sprint Goal is not compromised. A Product Owner does not dictate its contents.
Common mistakes
The commitment associated with the Sprint Backlog is the Sprint Goal, not the exact list of tasks. Because it changes constantly, teams keep it visible on a physical or digital board so progress toward the goal is transparent at any moment.
Example
During Sprint Planning, Developers break three Product Backlog items into eleven tasks and post them on the team's Kanban board as the Sprint Backlog.