A sponsor asked the product owner to deliver the highest-ROI functionality as soon as possible. Which artifact should the project lead use to track benefits?

The product backlog is a prioritized list of features, functions, requirements, and enhancements that need to be developed for a product. It is a living artifact that is continuously refined and re-prioritized based on business value, risk, and dependencies. Since the sponsor specifically asked for the highest-ROI functionality, the product backlog is the appropriate artifact to track and manage these items to ensure they are delivered as soon as possible. The requirements backlog is a less common term and typically refers to a subset of the product backlog focused solely on detailed requirements. The project charter formally authorizes the project but doesn't track ongoing benefits or functionality. Project scope defines what is and isn't included in the project but isn't a dynamic tracking tool for prioritized features.