This is a follow on from UML Profile for Benefits Realisation Management – 1. In that post I described the basic UML profile I have created for modelling project benefits in line with [Bradley] and [Ward & Daniels]
Having started to apply the profile successfully, I wanted to extend it to model measures,
These were modelled by meta-classing Class
Extending Benefits Model with Measures As can be seen from this diagram, I have added a number of tagged values (which are modelled as attributes in the UML profile) to cover off the typical data that needs to be captured in relation to a measure.
I wrote yesterday about using a general purpose UML modelling tool to create project Benefit Maps.
In that post I described using Enterprise Architect's ability to create custom UML profiles to create the beginnings of a custom modelling language for project benefits management.
In this article I walk through the basics of that UML profile.
Classes The first task was to model the core objects of the benefits model – Objectives, Benefits, Disbenefits, Business Changes and Enablers.
Benefits Realisation Management is one of those classic programme / project disciplines that “everyone” agrees is a great idea, which in my experience is more overlooked than observed.
The main sources in the literature I’m aware of are books by Bradley and Ward & Daniels. I’ve also had the privilege of learning directly from Gerald Bradley, so my own approach is very much influenced by his work.
A key tool is the use of visual maps, both interactively with stakeholders to discover benefits, and then as a way of presenting and communicating the complex causal links between an IT investment and the benefits it allegedly supports.
I’ve just got my hands on Benefit Realisation Management: A Practical Guide to Achieving Benefits Through Change by Gerald Bradley.