13.0 Implementation Phase

  • User manual documentation standards and guidelines must exist and be periodically reviewed. A process must exist to determine whether user manuals comply with set standards.
  • A process in the project management methodology to be sure user manuals are developed and distributed on time along with updates to users who need them.
  • Some end users must be allowed to review user manuals and provide feedback for updated before they are finalized.
  • A procedure must be in place to be sure third parties are informed of expectations during implementation steps.
  • The project management methodology must provide a process to be sure the system is formally authorized by the system owner and other appropriate management before it is placed into production. The system must meet the security design requirements. Management must accept any residual risk.
  • A process must be created and used to distribute production software to all authorized departments and users. The distribution media must utilize a method (such as a hash or CRC check) to ensure integrity of the installation software as part of the installation.
  • The software distribution process must include logging of what software has been sent to who, when, on what media, where the software is to operate, and license number where appropriate.

Project Implementation Plan

  • An implementation plan must be developed for each project.
  • The project implementation plan must provide resource requirements for implementation, implementation steps, and information about anything the project is dependent upon for implementation.
  • The project implementation plan must cover user training, equipment acquisition, equipment installation, site preparation, installation of software including changes, operating procedures. It should include any conversion activities to convert to a new system from an old one and consider how to keep the business functionality supported during conversion.
  • The project implementation plan must provide roles and responsibilities of those involved and consider the role of third parties involved.
  • The implementation plan must be used to guide implementation activities.
  • The project implementation plan must specify whether the implementation is in phases or as one effort.
  • The project implementation plan must consider the schedule and budget.
  • The project implementation plan must comply with organizational change management procedures and allow time for them.
  • The project implementation plan must provide procedures for rollback and recovery in the event that the implementation fails or is inadequate to provide business needs. Criticality of the business needs must be considered.
  • The project implementation plan must include time and provide for testing after the system is in production where required. Parallel or pilot testing may be required. If post implementation testing is done, a process to determine its success and conclusion must be provided.
  • The system owner and IT management must review and approve the project implementation plan before it is used.

Post Implementation Review

  • The project management methodology must allow a review of results after the implementation of the system. System requirements must be compared with actual system capabilities. Results of the review must be formally documented using post-implementation review procedures. The review results must be provided to the stakeholders owners of the system, and information technology management. The review must consider whether the functionality was provided in the most cost effective manner.
  • The review must examine possibilities for adding business value by allowing other business processes to use the system. Adding system value by making economical system changes should be considered.
  • The review looks at objectives met or not met, costs, timelines, benefits of the system such as cost savings of having an automated system, security and business risk, documentation created and still required, any shortfalls of the system, and overall quality.
  • The post implementation review must be conducted within three months of the project going into production.
  • The review must consider the original project requirements and definition along with any agreed to changes.
  • The review must obtain opinions of stakeholders, users, the system designers, the system implementers, and business groups with a stake in the project.
  • A policy must be put in place that specifies how often reviews (certification and accredidation) of the system to compare the system requirements to the actual capabilities. Requirements must include security requirements.
  • Any discrepancies found in the post implementation review must be acted upon promptly. The project management methodology must provide a process to ensure this is done and it is management's responsibility to be sure this is done.

Processes Required

  • Process for delivering software
  • Process of certifying and accreditating the system.
  • Process to ensure discrepancies found in post implementation review are acted upon promptly.