1 Project Characteristics vs Analysis Method

 

When deciding what kind of stakeholder analysis methodology you should use for your project, you should as a start classify the project into two main groups:


  1. -“one-of” project, this kind of project is unique and has never been done, and will not be done in the future

  2. -repetitive project, the same kind of project has been done, or will be done in the future


Here´s some factors you have to consider before you choose the method, either OO or function-oriented analysis:


  1. -“lessons learned”, the project will be based upon experience from earlier and similar projects

  2. -re-use of experience, calculations, people and procedures

  3. -support by a computer system implemented on a previous project, and configured for the new project

  4. -how dynamic is the project in terms of varying tasks, workload, people and procedures




















If it looks like the object oriented approach is the most relevant, this is what you have to do:

  1. -stakeholders will be defined by relevant information (“attributes”) and general behavior (“operations”). “Similar” stakeholders will be grouped into classes and properties will be inherited between classes and instances of stakeholders. Behavior towards the project will be defined on the stakeholder´s association with the project and attitude/goals (“link attributes”).

  2. -The project will identify stakeholder strategies with respect to these associations.


The object model is basically a static model. “Lessons learned” on behavior and successful strategies will be accumulated in the object model for later re-use in new projects.


The stakeholder´s behavior towards the project will typically vary during the execution timeline of the project (“dynamic model”) phases (study, engineering, construction, commissioning), and also related to the project´s use of cost, time and resources. The stakeholders will typically do “actions” towards the project, and that may result in certain “events” in the project. This may lead to that the project´s internal processes are going from one “state” to another.


The project´s traditional “functional model” is how internal calculations (“transformation of values”) are performed, integrated with the object- and dynamic models of the project.