8.8 Phase Completion Approval Signoff Completed

< Day Day Up >

8.8 Phase Completion Approval Signoff Completed

This is the last step in the evolution of the project. In reality, when this signoff is completed, it signals the end of the program. Technically, the SPMO will maintain all documentation and history of the project until this deliverable has served its purpose and is shelved or replaced by another. When that happens, the SPMO will have the Project Sponsor or Executive Stakeholder place the final nail in the coffin by signing this Phase Completion Signoff. Doing so kicks off the final process in the SEP life cycle, Project Closeout, which is discussed in the next chapter.

< Day Day Up >

8.9 Chapter 8 Review

To a development team, what is significant about the Support phase?
What are the six key tasks the Core Team must complete during the Support phase?
What is a Software Transition Plan?
What purpose does the MIS Hardware/Software Handoff Letter serve?
What are the three key sections every Support Plan should contain?
Define change management.
What is configuration control?
What key points should you remember when creating an SLA?
List the basic components of an SLA.
What is a Help Desk Checklist used for?

< Day Day Up >

Chapter 9: SEP Phase VIII-Project Closeout

Overview

Project Closeout is the final step in drawing the project to a close. Now, let's take a moment and, as always, review the SEP Phase VIII roadmap (Figure 9.1). In the Completion phase, you will perform all actions necessary to end project work and review project management performance. The postmortem meeting and its corresponding report should provide an effective means to reflect on lessons learned and battles won (and lost). It should be used to improve on the overall process for future projects.

click to expand
Figure 9.1: SEP Phase VIII Roadmap.

< Day Day Up >

9.1 Disposition Phase

Disposal actions should be implemented to either eliminate a large part of a system or close down a system and end the life cycle process. The system in this phase has been declared surplus and/or obsolete and is or will be scheduled for shutdown. The chief emphasis of this phase will be to ensure that data, procedures, and documentation are packaged and archived in an orderly fashion, making it possible to reinstall and bring the system back to an operational status, if necessary, and to retain all data records in accordance with corporate policies regarding retention of electronic records.

The Disposition phase represents the end of the system's life cycle. It is usually initiated by the SPMO when a product is ready to be replaced or taken offline. A Disposition Plan should be prepared to address all facets of archiving, transferring, and disposing of the system and data (as described previously). Particular emphasis shall be given to proper preservation of the data processed by the system so that it is effectively migrated to another system or archived in accordance with applicable records management regulations and policies for potential future access. The system disposition activities preserve information not only about the current production system but also about the evolution of the system through its life cycle.

The objectives for all tasks identified in this phase are to retire the system, software, hardware, and data. The tasks and activities actually performed depend on the nature of the project. The disposition activities are performed at the end of the system's life cycle. The disposition activities ensure the orderly termination of the system and preserve vital information about the system so that some or all of it may be reactivated in the future if necessary. These activities may be expanded, combined, or deleted, depending on the size of the system.

< Day Day Up >