PMP · Question #905
A project sponsor asked the product owner to deliver the functionality that provides the highest return on investment (ROI) as soon as possible. Which artifact should the project lead use to track ben
The correct answer is B. Product backlog. To deliver functionality with the highest ROI as soon as possible, the project lead should use the product backlog. The product backlog is dynamically prioritized, often by business value or ROI, to guide development.
Question
A project sponsor asked the product owner to deliver the functionality that provides the highest return on investment (ROI) as soon as possible. Which artifact should the project lead use to track benefits?
Options
- ARequirements backlog
- BProduct backlog
- CProject charter
- DProject scope
How the community answered
(28 responses)- A4% (1)
- B86% (24)
- C4% (1)
- D7% (2)
Why each option
To deliver functionality with the highest ROI as soon as possible, the project lead should use the product backlog. The product backlog is dynamically prioritized, often by business value or ROI, to guide development.
A "requirements backlog" is a generic term that might overlap with a product backlog, but "product backlog" is the specific agile artifact explicitly designed for prioritizing features by value.
In Agile projects, the product backlog is a dynamic, prioritized list of all the features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product. Items in the product backlog are typically ordered by business value, risk, dependencies, and necessity, making it the primary artifact for tracking what functionality delivers the highest return on investment and guiding the team's work to deliver those items first. The product owner is responsible for maximizing the value of the product and the work of the development team, which involves continuously refining and prioritizing the product backlog based on ROI and stakeholder needs.
The project charter defines the project's purpose, objectives, and high-level scope, but it doesn't serve as a dynamic artifact for prioritizing and tracking individual features for ROI delivery during execution.
The project scope defines what is and is not included in the project, but it's not a dynamic list prioritized by ROI for incremental delivery; it's a boundary document.
Concept tested: Agile product backlog prioritization for ROI
Source: https://www.scrum.org/resources/what-is-a-product-backlog
Topics
Community Discussion
9
Olusegun A.Mar 22, 2026B is correct. The product backlog is the artifact in an adaptive environment where the product owner orders items by value, ROI, risk, or whatever prioritization makes sense for stakeholder value. When the sponsor wants the highest ROI delivered first, that reprioritization happens here, not in a requirements backlog or a predictive artifact like the project charter. The product backlog is the single source of truth for what gets built and in what order, so that is where you track it.
Luis F.Mar 24, 2026Agree with B, and just to add, the backlog is dynamic so the PO can reorder it anytime as ROI assumptions change, not just at sprint planning.
Ola B.Mar 9, 2026Leaned toward A but highest ROI ASAP screams prioritized product backlog.
Olusegun A.Mar 10, 2026Agreed, but the real driver is value-based prioritization in the backlog, not just having a prioritized backlog, since ROI sequencing is what gets you the highest value first in an adaptive environment.
Luis F.Feb 28, 2026B is right, the product backlog is where you prioritize by value and ROI in agile. Quick question though, does anyone know if the PMP actually expects us to map ROI directly to backlog item priority or if it is just implied through the ordering?
Dervla O.Mar 3, 2026B is correct, and on the PMP the ROI mapping is implied through backlog ordering rather than called out as an explicit calculation step, so focus on the concept that higher-value items rise to the top and you will be fine.
Dervla O.Mar 25, 2026Going with A, since highest ROI items get prioritized first in the requirements backlog.
Zlatan X.Mar 26, 2026B is correct here, Dvela. The stem is pointing to weighted ranking and prioritization of requirements against multiple benefit criteria, which is the definition of requirements prioritization, not simply ROI - first sequencing in the backlog.
Zlatan X.Feb 25, 2026B is correct. The product backlog is the artifact where features and user stories are prioritized by business value and ROI, which aligns perfectly with the sponsor's request to deliver the highest-return functionality first. Think of the backlog as the benefits realization engine for an agile component, where sequencing directly drives value delivery. The requirements backlog is a trap because it sounds close, but it lacks the prioritization-by-value dimension the sponsor is asking about. One thing I always wrestle with at the program level: how do you aggregate product backlog ROI metrics across multiple agile components to report consolidated benefits realization to a steering