Update Sprint Backlog
During Sprint Planning, the Scrum Core Team works together to build the Sprint Backlog, listing all work the team plans to finish during the Sprint.
Key Points
- Occurs in the Sprint Planning meeting with the Scrum Core Team.
- Produces a Sprint Backlog that outlines the tasks selected for the Sprint.
- Tasks are broken down and sized to match team capacity and the Sprint Goal.
- The Sprint Backlog is updated as new information emerges during the Sprint.
Example
At the start of a two-week Sprint, the team reviews the top Product Backlog items, agrees on a Sprint Goal, decomposes selected items into tasks (e.g., design API endpoint, implement service, write tests, update user guide), estimates each task, and records them in the Sprint Backlog. As the Sprint progresses, they adjust the backlog to reflect completed and newly discovered work.
PMP Example Question
When is the Sprint Backlog created, and who is primarily responsible for it?
- During Daily Scrum by the Scrum Master
- During Sprint Planning by the Scrum Core Team
- During Release Planning by executive sponsors
- At project kickoff by the Product Owner
Correct Answer: B — During Sprint Planning by the Scrum Core Team
Explanation: The Sprint Backlog is formed in Sprint Planning by the Scrum Core Team, which selects and decomposes work into tasks for the upcoming Sprint.
HKSM