Where in the transformational flow would the Benefits Map normally be created?

MSP states that during ‘Defining a Programme’ the programme team develops the detailed benefits management products, including the Benefits Management Strategy, Benefits Profiles and the Benefits Map. The map is built once the vision and preliminary list of benefits (from ‘Identifying a Programme’) are available, so that cause-and-effect linkages between programme outputs, intermediate outcomes and strategic objectives can be modelled before delivery starts. It is therefore created in ‘Defining a Programme’, not earlier or in later delivery/realization stages.

A. Identifying a Programme – only outlines/high-level benefits are captured; no detailed mapping is carried out.
C. Managing the Tranches – governs delivery of projects; benefits map should already exist to guide this work.
D. Realizing the Benefits – focuses on tracking and harvesting planned benefits, using the previously created map.

1. AXELOS

“Managing Successful Programmes”

2011 edition

Appendix A

Table A.1 – Documents produced in each transformational flow; Benefits Map listed under ‘Defining a Programme’ (pp. 226-229).

2. AXELOS

“Managing Successful Programmes”

2011

Ch. 9.3.2 ‘Benefits management information products’ – description of Benefits Map creation during programme definition (pp. 135-136).

3. Cranfield University School of Management course notes

“Programme Management & MSP”

Lecture 4: Transformational Flow – slide set shows Benefits Map developed in Definition phase (Section 4.2).