Scrum Question
What is the major difference between Product Backlog and Sprint Backlog?
A. The Product Backlog is equal to the Sprint Backlog
B. The Product Backlog is a subset of the Sprint Backlog
C. The Sprint Backlog is a subset of the Product Backlog
D. The Sprint Backlog is owned by the Product Owner
➡️➡️ Slide below to see the answer and a short explanation.
TIP: The keyword here is MAJOR DIFFERENCE, so there might be more than one correct answer but you should outline the MAJOR DIFFERENCE. The correct answer here is C
RELATED: Multiple Scrum Teams Working on the Same Sprint Start Date
As usual, I always suggest going through the Scrum Guide to repass and study the meaning of Product Backlog, Sprint Backlog, their use within Scrum, and their respective owners or you can go through the next sections with extracts from the Scrum guide.
What is the Product Backlog?
Here are some parts taken from the Scrum Guide that will help you understand the meaning of Product Backlog in Scrum:
✓ What is the Product Backlog? |
✓ Product Owner is accountable for the Product Backlog  |
Sprint Backlog and Product Backlog during Sprint Planning
✓ Developers select items from the Product Backlog to include in the current Sprint |
 ✓ How does work on each Backlog Item gets done?  |
✓ What happens to the Product Backlog during Sprint Review?  |
Sprint Backlog and Product Backlog during the Sprint
✓ The developers are accountable for creating the sprint backlog i.e. the plan for the Sprint |
✓ Sprint Backlog is a plan for and done by developers and is composed of a Sprint Goal a set of Product Backlog Items and a plan to deliver the increment. |
 ✓ Sprint backlog can be changed as long as it doesn’t endanger the Sprint Goal by negotiation with the Product Owner. Product Backlog can and should be refined continuously as needed.  ✓ The daily is done to adjust the Sprint Backlog as necessary adjusting the upcoming work and checking the progress towards the Sprint Goal  |
References:
- Scrum Guide, 2021
- Introduction to the Nexus Framework Whitepaper@ Scrum.org by Simon Bourk & Patricia Kong, 2016