Effective Software Project Management

The Closing Phase

Closing a project is often the most overlooked of the phases of the project life cycle. You have another project waiting for you, and you are behind schedule. Your current project is finished, and there is nothing you can do about it any longer. It seems hard to devote any time to a completed project when you have a new one staring you in the face.

Both Linear SDPM strategies have the same closing activities. Once requirements have been validated and the acceptance test procedures met, the project enters the formal part of the Closing Phase. There is the sign-off by the customer that the project can truly enter the closing activities.

Deployment Strategies

The deliverables are deployed into production status. For both the Linear SDPM strategy for the Standard Waterfall model and the Linear SDPM strategy for the Rapid Development Waterfall model there will be only one deployment. All deliverables are put into production status at one time. For cases where you have multiple releases, you can refer to the Iterative, Adaptive, and Extreme SDPM strategies later in the book. Deployment in the Linear SDPM strategy can happen following one of four different strategies.

• 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 ...