10.07.2015 Views

Link to thesis - Concept - NTNU

Link to thesis - Concept - NTNU

Link to thesis - Concept - NTNU

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Degree of redundancySlackPrecisionChange management strategyAvoidchangesManagechangesFlexibility inproduct ordecision processCapacity <strong>to</strong> handlechangesAgreement onscopeHedge areas ofexpected changesFigure 3. Flexibility strategies in relation <strong>to</strong> redundancy and change management.Changes can be avoided by having slack resources in a project. Redundancy can be achieved by overspecificationof future functionality, so that future needs may be met without physical changes. Such needsmay emerge during the project execution, or after the project has been delivered. Redundancy can alsoenable front-end analyses of alternative project concepts, which require recourses and time but may avoidlater changes.Changes can also be avoided by precision in the project preparations, thus reducing the need for slack.Aiming at a clear agreement on scope represents a traditional project management approach – <strong>to</strong> zoom in onproject scope and then execute. After establishing the scope, project management aims at minimisingexternal flexibility.Changes can be managed if there is slack in a project organisation. High redundancy indicates a generalcapacity <strong>to</strong> manage a wide range of changes. Such slack can include budget reserves, time slack in plans andorganisation capacity <strong>to</strong> manage changes. On average, this increases project cost. However, it may still provecost effective if the alternative is that the project will face changes which it does not have the resources <strong>to</strong>manage.Finally, changes can be managed even with low redundancy, but it requires precision. In the process oflocking specifications, certain parts are locked later than others. Low redundancy requires an ability <strong>to</strong>identify and hedge areas exposed <strong>to</strong> changes. The late locking items must therefore be well defined and of alimited relative size.6.3. Flexibility options as flexibility driversIn the framework proposed in Figure 1, flexibility options where listed as flexibility drivers. This issupported by the discussion above. Of the studied projects, projects with a high planned flexibility in thedecision process also had a high actual flexibility in the decision process. Availability of flexibility optionsand redundant resources can serve as an invitation <strong>to</strong> adjustments. If there are possibilities for adjustmentsand iterations, it is likely that flexibility options will be utilised. This means that the presence (or knowledge)of flexibility enablers can work as a flexibility driver.6.4. Front-end as a key phaseFlexible the front-end phases are the least controversial aspect of project flexibility. This is particularlyrelated <strong>to</strong> external flexibility. Results presented in [7] indicates that minimizing external flexibility after thefront-end phase increases the likelihood <strong>to</strong> deliver projects on time and budget and according <strong>to</strong>specifications. One objective of front-end management is <strong>to</strong> provide a well defined framework for efficientproject implementation, including the identification of flexibility drivers, and appropriate introduction offlexibility enablers.

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

Saved successfully!

Ooh no, something went wrong!