Which artifact is described as a list of everything that could potentially be included in the project?

Which artifact is described as a list of everything that could potentially be included in the project?

• A. The sprint backlog
• B. The release plan
• C. The product backlog
• D. The increment backlog

Answer: (C)

In Agile product management, the item that acts as the living list of everything that could potentially be included in the project is the product backlog. It’s a dynamic, prioritized repository of all work items—features, enhancements, fixes, technical tasks, and even research work—that might someday be part of the product. The product owner manages it, continually refining and re-prioritizing items based on value, risk, and changing needs. Items stay in the backlog until they’re eventually selected for a sprint or release, at which point they move into more concrete planning. This makes the product backlog the best fit for a comprehensive list of potential work. The sprint backlog, by contrast, is a focused subset of items chosen to be completed in the upcoming sprint. A release plan outlines how and when features will be delivered across releases, rather than listing all possible future work. An “increment backlog” isn’t a standard Scrum artifact, since increments refer to the actually delivered product, not a backlog of potential items.

In Agile product management, the item that acts as the living list of everything that could potentially be included in the project is the product backlog. It’s a dynamic, prioritized repository of all work items—features, enhancements, fixes, technical tasks, and even research work—that might someday be part of the product. The product owner manages it, continually refining and re-prioritizing items based on value, risk, and changing needs. Items stay in the backlog until they’re eventually selected for a sprint or release, at which point they move into more concrete planning. This makes the product backlog the best fit for a comprehensive list of potential work.

The sprint backlog, by contrast, is a focused subset of items chosen to be completed in the upcoming sprint. A release plan outlines how and when features will be delivered across releases, rather than listing all possible future work. An “increment backlog” isn’t a standard Scrum artifact, since increments refer to the actually delivered product, not a backlog of potential items.