Which artifact collects all the work flowing to a team?

The product backlog is the correct artifact that collects all the work flowing to a team. It serves as a comprehensive list of features, enhancements, fixes, and any other requirements that need to be completed in order to create a product. The product backlog is dynamic and evolves continuously as new requirements are identified and priorities change, making it an essential tool for agile teams to organize and prioritize their work.

In contrast, the iteration backlog is more focused on the specific work to be accomplished during a single iteration. It pulls items from the product backlog to create a manageable scope for the team to work on within that time frame. This means it does not encompass all work flowing to the team, only the work that has been selected for that iteration.

The business backlog typically refers to a broader collection of work and needs but could vary from one organization to another in terms of its scope and definition. It does not specifically collect all the work flowing to a team in an agile context.

The release roadmap outlines the timing and scope of future releases but is not an artifact that collects work in progress. It is more of a strategic planning tool rather than a tangible list of tasks or items.

Therefore, the product backlog is the ideal artifact that captures and organizes all potential work flowing to