Which artifact is responsible for collecting all the work flowing to an Agile team?

The artifact that is responsible for collecting all the work flowing to an Agile team is the iteration backlog. This backlog consists of the items, often referred to as user stories or tasks, that the team commits to completing in the current iteration. The iteration backlog is dynamic and can evolve throughout the iteration as new work is identified, work that needs to be adjusted is discovered, or feedback is incorporated.

This artifact promotes transparency and collaboration as it reflects the team's active commitments. It allows team members to see what is currently being worked on and ensures that everyone is on the same page regarding the short-term goals of the iteration.

The other options do play important roles in the Agile framework. The business backlog encompasses a broader scope of initiatives that align with business goals but is not limited to what the team is actively working on in a specific iteration. The product backlog contains all the features and enhancements planned for the product in general, prioritizing them based on customer value and feedback but also not specific to a single iteration. The release roadmap outlines release plans over a longer timeline, detailing what features are planned for future releases without focusing on the immediate tasks, making it less relevant for the day-to-day work of the team.