Installing Project Deliverables

The second step of closing a project is to go live with the deliverables. This commonly occurs in computer systems work. The installation can involve phases, cutovers, or some other rollout strategy. In other cases, it involves nothing more than flipping a switch. Either way, some event or activity turns things over to the client. This installation triggers the beginning of a number of close-out activities that mostly relate to documentation and report preparation. After installation is complete, the deliverables move to support and maintenance, and the project is officially closed.

There are four popular methods to install deliverables, and the subsections that follow discuss them.

Phased Approach

The phased approach decomposes the deliverable into meaningful chunks and implements the chunks in the appropriate sequence. This approach would be appropriate in cases where resource limitations prevent any other approach from being used.

Cut-Over Approach

The cut-over approach replaces the old deliverable with the new deliverable in one action. To use this approach, the testing of the new system must have been successfully completed in a test environment that is exactly the same as the production environment.

Parallel Approach

In the parallel approach, the new deliverables are installed while the old deliverables are still operational. Both the old and the new deliverables are simultaneously in production mode. In cases where the new system might not ...

Get Effective Project Management: Traditional, Agile, Extreme, Sixth Edition now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.