sprintbacklogs

A sprint backlog is a Scrum artifact that contains the subset of product backlog items selected for the current sprint, together with a plan for delivering them. It represents the development team’s forecast for the sprint and is owned and managed by the team.

The sprint backlog is created during sprint planning. The team selects product backlog items that align with the sprint goal and the available capacity, then decomposes those items into actionable tasks and estimates the work required. The backlog typically includes the sprint goal, the chosen backlog items, the tasks needed to complete them, owners or assignees, and status or progress indicators.

The sprint backlog is a living document that the team updates throughout the sprint. As work progresses, tasks may be added, removed, or re-estimated based on new information. The backlog is used to track progress and to communicate what the team plans to deliver during the sprint. Changes to scope generally require collaboration with the product owner, while the team remains responsible for adjusting the plan to meet the sprint goal.

Relationship to other artifacts: the sprint backlog differs from the product backlog in that it is a short-term plan for a single sprint, not the full list of desired work. It complements the team’s task board or burn-down chart, which visualize progress and remaining work.

End of sprint: completed backlog items are reviewed and potentially accepted in a sprint review, while unfinished work is typically returned to the product backlog for re-prioritization or re-planning in a future sprint.