1. The PPSO SIG Spring 2006 Conference…

2. Agenda 9:45 - 10:30 Registration 10:30 - 11:15
“How to Identify Benefits” – John Zachar
11: :35
Coffee / networking
11: :45
“Changing Project Management Processes to Include Benefits Realisation” – David Marsh
12: :00
Lunch / networking
14: :45
“Extending Progress Reporting to Include Benefits” – David Marsh
14: :00
Tea / networking
15: :45
“Embedding changes” – Terri Kinton
16:00
Close

3. Benefits Driven Project Management
A Case Study

4. The background to the project
The problems to be faced
The conventional wisdom
The approach we took
The results
Lessons Learnt

5. The Background to the Project
The history of the function
Its evolution to the present day form
The new building
The constraints imposed on us:
To be able to move by……
The size of the new office and equipment
The change in attitude required of the staff

6. The Problems to be Faced
Existing process not fully known or understood
Existing technology not fully known or understood
Why things were done the way they were
The changes and their effect on the staff
It was part of a programme that did not really use a benefit driven approach
Was the organisation ready for this approach?

7. The Conventional Wisdom
Computerise what was done now
Fix User Requirements
It is box delivery project
Technology driven
Long wait before anything will happen

8. The Approach Taken Realised benefits early was possible if:
It was fully understood what the function was to do
Incrementally built the whole solution (not just the technology)
Convinced everyone that this new approach would work
Proved it would work before they moved

9. The Results Radical rethink of the function: simplifying
re-engineering
back to the real basis of the function
Discussion and agreement of that functionality
The model office office concept

10. Lessons Learnt Does not fit all projects
Organisation must be ready for this approach
The need to work in and with the Programme Credo may be a problem
The business must understand the reason why this approach is taken and what is in it for them
Its business value delivery - not deliverable development efficiency that counts
Needs to be explained in a risk management context

11. Summary
Ensure the project is benefits centred from day one in everyone's eyes
Plan for the delivery the benefits incrementally
MOSCO both way!
Benefits delivery efficiency is usually more important than project delivery efficiency 11 11 11 11