Benefits realization management (BRM), also benefits management, benefits realisation or project benefits management, is a project management methodology, often visual, addressing how time and resources are invested into making desirable changes.
BRM is used to manage the investment by organizations in procurement, projects, programmes and portfolios, and has been shown to increase project success across different countries and industries (although see:).
The popularity of BRM began in 1995 in the UK, when Scottish Widows created a Benefits Realisation method as part of its "Project Management Handbook", and rolled its use out across the entire firm. It grew in the UK with the inclusion of BRM by the UK Government in their standardized approach to programmes, "Managing Successful Programmes (MSP)".
Definitions.
Benefits realization management has four main definitions. 
The first definition is to consider benefits management as an organisational change process. It is defined as "the process of organizing and managing, such that the potential benefits arising from the use of IT are actually realized". 
The second definition perceives it as a process. Benefits management is defined by the Association for Project Management (APM) as the identification, definition, planning, tracking and realization of business benefits. 
The third definition is to apply this concept on project management level. Project benefits management is defined as "the initiating, planning, organizing, executing, controlling, transitioning and supporting of change in the organisation and its consequences as incurred by project management mechanisms to realize predefined project benefits". 
Finally, benefits realization management is perceived as a set of processes structured to "close the gap" between strategy planning and execution by ensuring the implementation of the most valuable initiatives.
Process.
BRM practices aim to ensure the alignment between project outcomes and business strategies: 
 ;templatestyles src="Template:Blockquote/styles.css" / ;"If value is to be created and sustained, benefits need to be actively managed through the whole investment lifecycle. From describing and selecting the investment, through programme scoping and design, delivery of the programme to create the capability and execution of the business changes required to utilise that capability, and the operation and eventual retirement of the resulting assets. Unfortunately, this is rarely the case."
Under BRM, outcomes are changes identified as important by stakeholders and can be strategic or non-strategic. A benefit is a measurable positive impact of change. A dis-benefit is a measurable negative impact of change. Successful BRM requires accountable people, relevant measures and proactive management.
As with all project management methodologies, BRM has clear roles and responsibilities, processes, principles and deliverables. The main roles are Business Change Managers (BCMs) who help the Benefits Owners (i.e. the main beneficiaries) identify, plan and review the expected benefits from the change and project managers who deliver the reliable capability on time and within budget. 
A generic BRM process is then as aside.
To identify the investment outcomes, pictorial views of the outcomes of interest on an "outcome map" (also called a "results chain", "benefits dependency network" or "benefit map") can be created. 
See next section.
This technique supports agreement of the outcomes sought as it shows the outcomes and relationships between them on a single page. They can be agreed upon and communicated clearly as a result.
Data can then be captured either separately or within a suitable modelling tool for each outcome that will include the benefit measures used for each, ownership and accountability information and information to support realisation management.
Benefit mapping.
Constructing benefits maps or graphs is usually done from right to left, with what is attempting to be achieved (often called objectives, strategic outcomes etc.) being the start point, then moving through intermediate outcomes to the things required to cause these to happen at the very left.
Benefits dependency networks.
The "benefits dependency network" (BDN) has five types of object within maps.
Benefits dependency map.
The "benefits dependency map" (BDM) also has five types of object on the maps
Results chain.
The "results chain" has four types of object on the maps.
References.
 ;templatestyles src="Reflist/styles.css" / ;