Exam PMP topic 1 question 879 discussion

To track benefits and return on investment (ROI), the project lead should use the Product Backlog (Option B). The Product Backlog contains a prioritized list of features, functionalities, and user stories, and it's a valuable tool for tracking the delivery of value and benefits throughout the project. The most valuable items with the highest ROI should be placed at the top of the Product Backlog and are typically delivered earlier in the project, allowing for the tracking of benefits as they are implemented and realized.

Check project scope.

In Agile project management, the Product Backlog is a prioritized list of all the features, enhancements, and fixes that need to be addressed in the product. It is ordered based on the value it delivers to the customer or stakeholders. Therefore, when the project sponsor wants to focus on delivering functionality with the highest return on investment (ROI), the project lead should refer to the Product Backlog. The items at the top of the Product Backlog are the highest priority and are typically the ones that provide the most value. Tracking benefits and return on investment can be effectively managed by managing and prioritizing the Product Backlog.

Product Backlog is specifically designed to manage and prioritize product increments based on their value and user needs. It can be adapted to accommodate ROI considerations by: Estimating the ROI of each backlog item: This can be done through techniques like cost-benefit analysis or net present value calculations. Prioritizing based on ROI: Backlog items with higher ROI can be moved closer to the top of the queue, ensuring the functionality with the highest ROI is delivered first. Tracking actual benefits realized: As functionalities are delivered, the project lead can track the actual benefits achieved and compare them to the estimated ROI, providing valuable insights for future iterations.

B is the answer

Why not D. Project scope offers more granular information that can be use to calculate the ROI?

The project charter typically outlines the high-level vision, objectives, stakeholders, and key milestones of the project. While it might not contain detailed tracking of benefits realization or a comprehensive Benefits Management Plan, it often highlights the overarching goals and expected outcomes of the project, which could include references to benefits or ROI.

Keyword is "track". The charter outlines the expected benefits, while the backlog tracks their priority & delivery/realization.

While the Product Backlog helps the development team understand what needs to be worked on next, it may not be the artifact used specifically for tracking benefits. The Project Charter (Option C) is often the document that outlines the expected benefits and return on investment for the project. It serves as a higher-level document that provides context and goals for the project, including the anticipated benefits.

The backlog is a well-defined list of tasks. According to Atlassian, a product backlog is a prioritized list of work for the development team that is derived from the roadmap and its requirements. The most important items are shown at the top of the product backlog so the team knows what to deliver first.