Implementation Phase

In this phase, the production system is installed, initial user training is completed, user documentation is delivered, and the post implementation review meeting is held. When this phase is completed, the application is in steady-state production. Once the system is in steady-state production, it is reviewed to ensure that we met all of the goals in the project plan for a satisfactory result.

The team may be regrouped again, to include specific expertise in installation and training.


User Training
The initial training classes for users are held, and training materials are delivered at the classes. Some help desk personnel should attend the initial user training class. More training classes can be scheduled later, as new personnel start using the application. Training is done on the user acceptance test system, accessing the test database or a special training database.

Distributed User Documentation
User documentation that was finalized in User Acceptance Testing is now distributed and in the users' possession.

Finalized System Documentation
System documentation corrected with all updates from the testing phases is handed over to production support.

Installed Production System
The production system is installed in the appropriate production environment or on the appropriate production server, and on any client workstations that require it.

Post-Implementation Review Summary
This report is produced after the post-implementation review meeting, and contains a summary of the project success criteria that were met, success criteria that were not met and reasons for the problem, what we can learn from the project to improve practices for the next project. In particular, the report should identify any techniques or practices used in this project that worked extremely well, and which the project team feels would benefit current and future projects.

Methodology Compliance Form
This form is initialized by the project team, and completed by a methodology representative who has reviewed the project documentation and found it acceptable. It is completed in Word.

At this time, no sample is available.


  1. The team arranges for the installation of the production system, possibly participating in the installation, as determined by the application transition team.
  2. Technical training is completed for support staff from DMS' Production Support team, Systems and Networking, and the Help Desk, as needed. This can include vendor training, in-house training, and knowledge transfer activities, according to the Transition Plan developed by the application transition team.
  3. All transition deliverables enumerated in the Transition Plan must be collected, validated, and approved by the end of this phase. These transition deliverables must include finalized system documentation.
  4. Training for clients is scheduled and held, using the User Acceptance Test system, and accessing either a test database or a special training database. Training materials are distributed at the classes.
  5. The production system is installed in the production environment, and on any client workstations that require it.
  6. The user documentation is delivered to the clients who will be using the system.
  7. The system goes through a shake-down period in production, with the full support of the application transition team, the project development team, and the production support staff assigned to the application.
  8. The application is turned over officially to Production Support at a turnover meeting, and the application users are notified that the application is now fully in production, and that all problem reports will be fielded by the Help Desk from this point forward. Once the system is turned over to production support, the production support team will be responsible for any maintenance or enhancements required for the system.
  9. The core team schedules the post-implementation review no more than 60 days after the system has been installed and implemented.
  10. The post-implementation review is held with the Project Office or methodology representative facilitating. At this meeting, the team discusses what went well, what went wrong, and what did we learn that we can carry forward into other projects. To determine what needs to be changed to ensure success in future projects, attention should also be paid to any risks that materialized (did the risk plan alleviate the problem; if not, why not?), or issues that were not resolved in a timely fashion.
  11. A representative from the Project Office or the methodology group produces the Post-Implementation Review Summary report, and distributes it to all meeting attendees, project sponsors, the Project Office, and the methodology group. A Word template is available for this report.