Sprint Backlog
The collection of work the Scrum team selects for the sprint, plus their plan to complete it within the sprint timebox.
Key Points
- Built during Sprint Planning from Product Backlog items the team forecasts for the sprint.
- Team-owned and continuously updated as understanding improves and new tasks are discovered.
- Makes progress transparent by showing tasks, estimates, and remaining work toward the Sprint Goal.
- Acts as the execution plan for the sprint; changes are expected as long as the Sprint Goal remains achievable.
Example
In a 2-week sprint, the team selects three user stories for the checkout feature. They break them into tasks such as "create payment API endpoint," "validate card input," "write unit tests," and "update help docs." These tasks form the Sprint Backlog and are updated daily as work progresses and new needs are found.
PMP Example Question
Which artifact lists the work the Scrum team plans to complete in the current sprint and is updated throughout the sprint?
- Product Backlog
- Sprint Backlog
- Increment
- Product Roadmap
Correct Answer: B — Sprint Backlog
Explanation: The Sprint Backlog contains the items selected for the sprint and the plan to deliver them, and it is continuously refined by the team during the sprint.