Benefit management should help the sponsoring organization and the customer secure the intended gains from project outcomes, and benefits should sit in the project plan where their delivery falls within scope. Goals and wanted gains should be set out, examined, ranked, recorded and shared with stakeholders, and planned activities should be defined so they can be tracked and governed. Work to identify and analyse benefits should begin while the project is still under consideration, with the sponsor agreeing gains alongside the sponsoring organization and stakeholders and entering them in the business case. After the project is set up, a fuller set should be set out, examined, ranked and accepted by the sponsor or another authorized body, covering priorities, possible harmful effects, further gains, the organizational and social change required, the stakeholders for each gain, fit with strategy, performance measures and reporting, dates, and confirmation that planned outputs and outcomes will deliver them. Benefit monitoring should follow progress through the life cycle toward outcomes and their impact on intended gains, gather performance measures for each gain and report and share benefit status. The project manager should inform the sponsor about how plan changes affect benefits, and before the project closes, responsibility for realizing gains later should move to the stakeholders who will deliver them. Where benefits inside project scope differ from the plan, corrective action should be taken and preventive action used when needed.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.