Categories: Benefits, Benefits Realization, Change Management, definition, PgMP, Program Management, qualify, quantify, transition, Value
Benefits Realization PMI Model – Standard for Program Management Version 3.0
The Project Management Institute® (PMI) has defined a Benefits Realization model for a Program Manager to use to help the company capture the expectations of an investment. The concept of the model is to provide a structure from the initial planning through to actual realization (or booking) of the benefits into a new Business As Usual change. The five steps are loosely structures to be hierarchical in flow, but allows for a progressive elaboration approach as more information becomes available during program implementation.

Benefits Identification
This is the initial step of capturing the potential benefits that can be realized by the program. This step is analogous to a brain storming session and will result in a canonical listing of potential benefits. There are many sources for gathering this information including business documents, brainstorming sessions, extraction from a business plan, external factor analysis, organizational strategic objectives, and expert knowledge. Many organizations will group the list into various categories to assist in analysis and eventual ownership. The outcome of this step should be a list of potential benefits in a benefits register.
Benefits Analysis and Planning
This is the means of qualifying and quantifying benefits. If the benefits Identification step produces a canonical list of benefits, then each benefit needs to pass a “test” to see if it truly qualifies as a benefit, or to help prioritize benefits. The benefits register should contain the associated algorithms and business rules/logic required to define the value of the benefit. The analysis will also include setting an expectation for the value of the benefit and a relationship of the benefits against sequence, time, and dependencies. A significant portion of this step is to align company performance metrics (KPI) to be able to measure, demonstrate, the results of the implementation. The end result of this step should be the Benefits Realization Plan (BRP) which formally documents the activities required for achieving the program’s planned objective. Included in the Benefits Realization Plan is a program roadmap which documents the expected delivery of the value of the benefit against time. The BRP will also define how the benefits will be transition to operations at the end of component deliver and the sustainability expectations. The Benefits Realization Plan is a control document and needs to be baselined and managed under strict change control throughout the life of the program.
Benefits Delivery
This is the means of actually placing the changes into the business and the start of seeing the expected benefits in the business reporting infrastructure. Since Programs will include multiple components, the delivery will be an iterative process and will span from the first project completion through to Program Closure. Using the baselined BRP, the program resources will conduct monitor and control activities to analyze the results and prescribe corrective action. Part of this prescriptive corrective action is to ensure the Benefits Register is aligned with the monitor and control activities. The final litmus test of the benefit delivery is to ensure the results are properly accounted in the company Profit and Loss (P&L) applications (or they are “booked”).
Benefits Transition
This is the means of recognizing the programs have defined ends and that benefits might be realized long past the closure of the program. The Benefits Owner will eventually assign benefits realization to an operations function where it measures the benefits as part of a “Business As Usual” process. This implies that monitor and control and associated prescriptive action is no longer the responsibility of the Program manager, but not the operations manager.
Another important aspect of the Benefits Transition is that operations team will often view a suite of benefits as one item. For example there may be six benefits included in a project software enhancement, the operations team will most likely look at that as one enhancement. Therefore, the benefits transition process, and associated artifacts, will consolidate coordinated benefits into the package to east transition. The outcome of this phase will be the standardized reporting of benefits to associated benefit and business owners.
Benefits Sustainment
Finally, benefits need to be sustained over the lifecycle of the change initiative. Many times the benefits will be forecasts over time, as defined in the benefits roadmap, and the time frames will expand past the life of the program. After benefits are transitions, they need to be sustained.
Monitor and control and taking corrective action is a portion of the sustainment steps, but it can include much more. It is possible that during the lifecycle of the change that previously unidentified benefits are realized, these “emergent” benefits should be documented and through the use of structured change control, incorporated into the benefits reporting models.
Conclusion
The PMI Benefits realization model defines a structured set of phased to support the identification of, analysis of, monitoring and control of, the transition of, and the sustainment of benefits throughout the lifecycle of the change. The model also encompasses the “care and feeding” of benefits after transition to operations and helps to validate the true return on investment to the organization. Benefits Management needs to be incorporated into an organizations knitting and be considered in all aspects of the program.
Sources
Letavec, Craig J. Strategic Benefits Realization: Optimizing Value through Programs, Portfolios and Organizational Change Management. Plantation, Fl.: J. Ross, 2014. Print.
The Standard for Program Management. Vol. 3. Newtown Square, Pa: Project Management Institute, 2013.
We're All In This Together !!!
Dave



