"You can't wait for inspiration. You have to go after it with a club."
-- Jack London (1876 - 1916)

Management Tips

{Project Name}

Implementation Plan

Remove italicized comments within this template from the final document

INDEX

CONTACT & DISTRIBUTION
REVISION HISTORY
QUALITY CONTROL
Development Methodology
Change Control
Audit
INSTALLATION PLAN
Purpose
Installation Requirements
Implementation Approach
Implementation Procedures
TEST INSTALLATION
DATA CONVERSION TEST
SYSTEM INTEGRATION TEST
USER TRAINING
LIVE INSTALLATION / DATA CONVERSION
Contingency Plan
BACK-UP PROCEDURES
RESTORING DATA FILES
RESTORING PROGRAMS
Retirement of Legacy Systems
SCHEDULING RETIREMENTS
BACKING UP LEGACY SYSTEM
REMOVAL OF LEGACY SYSTEM
Schedule
APPENDIX A - SUPPORTING DOCUMENTS
APPENDIX B - GLOSSARY

CONTACT & DISTRIBUTION

Prepared by:

Include the name of the document's author, author's telephone and email address.

Contributors:

List contributors to this document, and the nature of their contributions.

Primary Contact:

The primary contact is usually the Project Leader. Include email link.

Distribution:

List the mailing list, Usenet group, web address, or other method of intended distribution.

REVISION HISTORY

Date of Revision	Revised By	Description of Revision	Affected Modules

QUALITY CONTROL

Development Methodology
For the purposes of this project, we are using a simplified Project Life Cycle, the details of which can be found at www.kuhnllc.com.
Change Control
Detail the change control plan in two contexts:

The context of changes to the SPECIFICATIONS and DESIGN. Strongly discourage changes to the specifications and design. Encourage up-front thinking and you will be better able to maintain project focus as it proceeds.
The context of change control for documentation, source, and resources. List how revision control will be accomplished, where the revision control is located, who has access, etc.

Audit Plan
How do we know we did a good job? Testing and Peer Review should be addressed here.

INSTALLATION PLAN

Purpose
Describe this document with an overview of the system. This document is not designed to be used with an end-user point and click type install, but is geared toward a more technically oriented scenario where conversion of an existing complex system is an issue.
Implementation Requirements
Describe the people and resources required for installation of the system. Include the following:

PEOPLE

TOOLS

HARDWARE

SOFTWARE

OTHER

Implementation Approach
High -level overview of the implementation plan. Describe what is to be accomplished.
Implementation Procedures
Do what makes sense for your installation. Add or remove steps as appropriate.

TEST INSTALLATION
A test of the installation should be performed prior to the date that the system is scheduled to be deployed.
DATA CONVERSION TEST
To be performed if existing data is to be converted to the new system. A "dry run" of the data conversion must be accomplished.
SYSTEM INTEGRATION TEST
A system/integration test should be done with the converted test data, if available.
USER TRAINING
Assuming the test installation and data conversion were successful, user training should be performed with the test installation. Users should not be present during any of the preceding steps. Refer to the Training Plan for training guidelines.
LIVE INSTALLATION / DATA CONVERSION
Having had a successful dry run, you can now install the system into production. If this means simply emptying or re-populating the data files, then you should test this procedure as well to make sure it will go smoothly. The goal is to have zero problems encountered during the actual installation.

Contingency Plan

BACK-UP PROCEDURES

RESTORING DATA FILES

RESTORING PROGRAMS

Retirement of Legacy Systems

SCHEDULING RETIREMENT

BACKING UP LEGACY SYSTEM

REMOVAL OF LEGACY SYSTEM

Schedule
High-level schedule of implementation.

APPENDIX A - SUPPORTING DOCUMENTS

Reference via hypertext link

APPENDIX B - GLOSSARY

Reference via hypertext link