Msp benefits profile template

It is typically developed during the definition process of a project or programme following requirements management. The profile includes sections that describe the benefit or dis-benefit and how it will be realised and measured. Each benefit or dis-benefit should have a unique identifier.

This is primarily used for cross-referencing in reports and supporting documentation. Any assumptions made in estimates of cost or value, design of change required or availability of resources. Benefits usually depend upon outputs and therefore the projects that produce them. A benefit may depend upon multiple outputs or even products and events external to the current project or programme.

All such dependencies should be documented here. The business area affected by benefit or dis-benefit should be identified along with a description of the following:. The benefit recipient is the person who most stands to gain from the benefit. These are sometimes the same person, but sometimes they are not.

Realization Start and Finish Dates: It is important to set these dates so that we can know when we should be measuring benefits.

Mechanisms: These, in my opinion, are the absolute core of successful benefits management. For example, imagine our Personnel Systems Project will provide a faster connection and processing speed that will drive a benefit of reduced processing cost. The types of things we would do about that could include:. Typically you should try to keep this to the top five or six things you want to do. You also need to make sure that there is agreement to each of the mechanisms, because your next step is to nominate the review points for those mechanisms.

For example, the restriction of tender responses needs to be checked at a project gate before the request for tender RFT is released. Enforcing these gate checks is the most controversial and difficult part of benefits management. However, the results of this rigor can be staggering. Bradley describes a Benefits Map in terms of cause-effect. On the benefits map you realise benefits left-to-right, from enablers to business change to benefits. A benefit is the measurable improvement resulting from a change.

You should avoid setting up industry of measurement hopefully this measurement will fall out of normal information management. To save overhead you might only measure for the lowest level of Benefit.

There are differences in format and content between these versions but they are really different flavours of the same thing. Adzic, G. Mayfield, P. Visual mapping of benefits. Learning Leader. Thorp, J. Thank you for this very elegant explanation. I do have one question. For instance how do I construct the benefits? They answer two key questions: Why are we doing the programme?

How will we realise the benefits? Benefits Map. Benefits Dependency Map. Benefits Map Questions. Excellent post Steven! Thank you! I found this really insightful.