10.07.2015 Views

Link to thesis - Concept - NTNU

Link to thesis - Concept - NTNU

Link to thesis - Concept - NTNU

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4. Project stakeholders4. Project stakeholdersThis chapter analyses project flexibility from a stakeholder perspective. Projectstakeholders are actively involved in a project, or their interests may be positively ornegatively affected by a project. An analysis of flexibility in a stakeholder perspectivecalled for a distinction between internal and external project flexibility. Projectinternal flexibility relates <strong>to</strong> flexibility within defined scope. Project externalflexibility relates <strong>to</strong> adjustments of scope. The approach <strong>to</strong> flexibility held by thedifferent stakeholders is closely related <strong>to</strong> the incentives open <strong>to</strong> the stakeholders.Flexible projects have a value for those who can align a project <strong>to</strong> their priorities, butflexibility represents a cost for those who have <strong>to</strong> adapt.4.1 StakeholdersAccording <strong>to</strong> McElroy & Mills (2000), project stakeholders are persons or groups ofpeople who have a vested interest in the success of a project and the environmentwithin which the project operates. In a study of large engineering projects, Olander &Landin (2005) found that it is important for a project management team <strong>to</strong> identifystakeholders that can affect a project, and then manage their differing demandsthroughout the project stages. Stakeholders may be organisations or individuals. Thefollowing discussion is focused on four types of project stakeholders: owners, users,project management, and contrac<strong>to</strong>rs.It is the project owner that takes the risk related <strong>to</strong> the cost and future viability of aproject. Both these risks can <strong>to</strong> a certain extent be transferred <strong>to</strong> other ac<strong>to</strong>rs in aproject.Users can be described using a wide or a narrow definition. The wide definition ofusers includes all that use the result of the project (the hospital, railway companies,etc.). During the project preparation and execution, users are not easily identified.This means that projects usually interact with user representatives, who act on behalfof those who intend <strong>to</strong> use the result of the project. The narrow definition of ‘users’refers <strong>to</strong> such user representatives.The ‘project management’ stakeholder refers <strong>to</strong> the project manager acting on behalfof the project owner and the organisation supporting this function. Contrac<strong>to</strong>rs areresponsible for implementing the whole or part(s) of the project.Results presented in Paper 4 indicate that project owners and users are more likely <strong>to</strong>be positive <strong>to</strong>wards changes aimed at increasing the benefit side of the projects, orrelated <strong>to</strong> effectiveness. Stakeholders whose main responsibility lies on the cost sideof the project, such as project management and contrac<strong>to</strong>rs, are less likely <strong>to</strong> embracechanges. According <strong>to</strong> Kreiner (1995), the project management is made the guardianof efficiency. Müller & Turner (2005) claim that owners should impose mediumlevels of structure on project managers. Too much structure will not give the projectmanager sufficient flexibility <strong>to</strong> deal with any uncertainties that arise. Too littlestructure will lead <strong>to</strong> anarchy.17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!