Link to thesis - Concept - NTNU
Link to thesis - Concept - NTNU
Link to thesis - Concept - NTNU
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
5. Effectiveness and efficiencyconflicts related <strong>to</strong> scope changes can be identified. First, conflicts may ariseregarding quantification of the increase in effectiveness and reduction in efficiency.This is related <strong>to</strong> the high and unpredictable cost of change orders. The secondconflict source is linked <strong>to</strong> allocating responsibility for reductions in efficiency.Challenges in estimating the effect of changes orders are discussed by Eden, Williams& Ackermann (2005). They particularly point <strong>to</strong> problems in finding a reference pointwhich describes the performance of a project in a period when the project was notdisturbed by changes. Eden, Ackermann & Williams (2005) describes underlyingmechanisms for how changes can cause cost overruns. They point <strong>to</strong> non-linearrelations between changes and cost development.Project internal processes can be simulated, either ex ante <strong>to</strong> predict the outcome of aparticular project design or ex post <strong>to</strong> explain and illustrate causes and effects inprojects. Kunz, Levitt & Jin (1998) and Christiansen (1993) describe how principlesfrom general management research can be applied in a computer based simulationmodel. This type of simulation has been used as decision support <strong>to</strong> predict theoutcome of a particular project, as shown by Kunz, Rivero & Levitt (2000) and DNV(2000). Williams (2003) proposes combined use of causal mapping and SystemDynamics <strong>to</strong> analyse the effect of a delay upon a project.To quantify the effect of changes, Cooper & Reichelt (2004) have performedsimulations of the aggregated disruptions caused by changes. Their simulationspredicted that a change equivalent <strong>to</strong> 10% of the <strong>to</strong>tal project budget would causedisruptions amounting <strong>to</strong> 2.8 times the estimated size of a change.Løken (2005) tested this estimate on a major scope change (called ‘U96’) in aNorwegian hospital project (Nytt Rikshospital). Based on a cut-off in year 2000, thescope change isolated was estimated <strong>to</strong> 424 million NOK, equivalent <strong>to</strong> c.10% the<strong>to</strong>tal cost. At the same cut-off time, <strong>to</strong>tal cost overruns were estimated <strong>to</strong> 1,105million NOK. Simulations of Cooper & Reichelt (2004) then predict that such achange causes disruptions in the order of 2.8 times the estimated size of a change, or1,013 million NOK. One interpretation of this is that disruptions from the scopechange caused 92% the <strong>to</strong>tal cost overruns. This interpretation is supported by anevaluation report of the project (Arbeids- og administrasjonsdepartementet 2001). Theevaluation report claims that this particular scope change was a major contribution <strong>to</strong>the <strong>to</strong>tal cost overruns, even though there were other additional fac<strong>to</strong>rs.Paper 3 studied how change management was approached in quality assurancereports. The strong emphasis on scope change management in the quality assurancereports indicates that changes and flexibility are primarily treated as something <strong>to</strong> beminimised, or at least <strong>to</strong> have a strict regime for. Management of changes wasmentioned as a <strong>to</strong>p issue in half of the projects. In most cases, the purpose was <strong>to</strong>establish a structured management of scope changes in order <strong>to</strong> minimise the amountand size of the changes.Thus, at least two different strategies can be identified <strong>to</strong> manage scope changes:either <strong>to</strong> avoid changes or <strong>to</strong> reduce the negative impact from any changes that doarise. In the following, these two approaches for change management will bediscussed in relation <strong>to</strong> redundancy.25