02.02.2013 Aufrufe

2 management - School of International Business and ...

2 management - School of International Business and ...

2 management - School of International Business and ...

MEHR ANZEIGEN
WENIGER ANZEIGEN

Sie wollen auch ein ePaper? Erhöhen Sie die Reichweite Ihrer Titel.

YUMPU macht aus Druck-PDFs automatisch weboptimierte ePaper, die Google liebt.

Wolfgang Cronenbroeck<br />

change <strong>management</strong> list. It is recommended to precisely document the additional expense for<br />

the approved change, or the scope <strong>of</strong> the schedule delay as well as the cause for this.The project<br />

manager is responsible for monitoring the implementation <strong>of</strong> the change order.<br />

2.4 PROJECT COMPLETION<br />

After the project results are complete, the project must be formally brought to a conclusion.<br />

The project conclusion phase begins as soon as the last milestone in the project is accepted, <strong>and</strong><br />

all project results have been reached; then the project is, by definition, completed.<br />

The following belong to a proper project conclusion:<br />

– Final acceptance <strong>of</strong> the project results in accordance with the project contract<br />

– Closing presentation <strong>of</strong> the project results with the client<br />

– Final meeting with the project team.<br />

– Project conclusion report.<br />

After the project completion activities have been carried out, the project is formally ended, <strong>and</strong><br />

the project organization <strong>and</strong> infrastructure (space, user ID's, other project-supporting resources)<br />

are dissolved. Thus the project workers are again available for other tasks. A successful <strong>and</strong><br />

trained project team can thus be considered an important project result. The author recommends<br />

deploying such a team, unchanged, for a new project. This can ensure that starting difficulties<br />

<strong>and</strong> interpersonal friction are avoided in the new project, <strong>and</strong> the requisite transfer <strong>of</strong> know-how is<br />

assured. To the degree that there are subsequent activities (e.g. maintenance work, user support,<br />

others), the necessary work must be carried out. It should be made clear, nevertheless, that the<br />

subsequent work is not a part <strong>of</strong> the project.<br />

2.4.1 FINAL INSPECTION<br />

Final inspection by the client is the first step in the conclusion phase. Final inspection <strong>of</strong> a project<br />

<strong>and</strong> its results is comparable with partial inspection <strong>of</strong> milestones in the course <strong>of</strong> the project. Fi-<br />

nal inspection is in any case a required activity, <strong>and</strong> requires preparation by the project manager.<br />

The project results achieved are assessed by the client, <strong>and</strong> compared to the requirements in the<br />

project contract in the context <strong>of</strong> final inspection. Earlier milestones or partial acceptance are also<br />

included in the final inspection. Acceptance is to be communicated to the contractor by the client.<br />

The project results according to the project contract, including documentation, are provided for<br />

inspection. It makes sense to conduct an inspection meeting at the beginning <strong>of</strong> the inspection<br />

period.<br />

In the inspection meeting results to be inspected are presented in a summary version, <strong>and</strong> the<br />

procedure for inspection is settled between the client <strong>and</strong> the contractor.<br />

232

Hurra! Ihre Datei wurde hochgeladen und ist bereit für die Veröffentlichung.

Erfolgreich gespeichert!

Leider ist etwas schief gelaufen!