How do product backlog and sprint backlog differ?

How do product backlog and sprint backlog differ?

• A. Product backlog contains all desired features; sprint backlog lists items selected for the current sprint.
• B. Product backlog lists items for current sprint; sprint backlog contains all features
• C. Product backlog is fixed; sprint backlog is updated yearly
• D. Product backlog contains only defects; sprint backlog contains new features

Answer: (A)

The main idea here is distinguishing long‑term planning from sprint execution. The product backlog is the comprehensive, prioritized list of everything that might be built for the product—features, improvements, bug fixes, technical work—continuously refined and reprioritized by the product owner as new information comes in. The sprint backlog is a plan for the current sprint: a subset of items pulled from the product backlog that the team commits to delivering in the upcoming sprint, broken down into actionable tasks for the team to complete during that sprint. So the statement that the product backlog contains all desired features and the sprint backlog lists items selected for the current sprint best reflects this distinction. The other options mix up scope and timing—for example, reversing what belongs to each backlog, claiming one is fixed or updated on a yearly basis, or restricting the product backlog to defects only.

The main idea here is distinguishing long‑term planning from sprint execution. The product backlog is the comprehensive, prioritized list of everything that might be built for the product—features, improvements, bug fixes, technical work—continuously refined and reprioritized by the product owner as new information comes in. The sprint backlog is a plan for the current sprint: a subset of items pulled from the product backlog that the team commits to delivering in the upcoming sprint, broken down into actionable tasks for the team to complete during that sprint.

So the statement that the product backlog contains all desired features and the sprint backlog lists items selected for the current sprint best reflects this distinction. The other options mix up scope and timing—for example, reversing what belongs to each backlog, claiming one is fixed or updated on a yearly basis, or restricting the product backlog to defects only.