What is the difference between a product backlog and a sprint backlog in Agile/Kanban contexts?

What is the difference between a product backlog and a sprint backlog in Agile/Kanban contexts?

• A. Product backlog lists all desired features or work.
• B. Sprint backlog contains all features for the entire project.
• C. Sprint backlog contains selected items for completion within a specific iteration.
• D. The backlog types are the same and interchangeable.

Answer: (C)

In Agile planning, think of the product backlog as the master, long-term list of everything the product might need, constantly refined and prioritized by the product owner. It represents the full spectrum of desired features, enhancements, fixes, and other work, with no fixed time horizon. The sprint backlog, by contrast, is a short-term plan derived from that master list. It consists of the items selected from the top of the product backlog to be completed in the upcoming iteration, broken down into actionable tasks with a clear implementation plan. It is time-boxed and scoped for a specific sprint (or iteration), providing the team a concrete set of work to finish. In Kanban, there isn’t a fixed sprint, so you don’t commit to a specific iteration's worth of work in advance. Instead, you pull items from the backlog as capacity allows, maintaining flow and limiting work in progress. The key distinction remains: the product backlog is the broad, ongoing list, while the sprint backlog is the focused subset the team intends to deliver in the current window.

In Agile planning, think of the product backlog as the master, long-term list of everything the product might need, constantly refined and prioritized by the product owner. It represents the full spectrum of desired features, enhancements, fixes, and other work, with no fixed time horizon.

The sprint backlog, by contrast, is a short-term plan derived from that master list. It consists of the items selected from the top of the product backlog to be completed in the upcoming iteration, broken down into actionable tasks with a clear implementation plan. It is time-boxed and scoped for a specific sprint (or iteration), providing the team a concrete set of work to finish.

In Kanban, there isn’t a fixed sprint, so you don’t commit to a specific iteration's worth of work in advance. Instead, you pull items from the backlog as capacity allows, maintaining flow and limiting work in progress. The key distinction remains: the product backlog is the broad, ongoing list, while the sprint backlog is the focused subset the team intends to deliver in the current window.