Go Live

Move the new application into production
  • Implementation Plan
  • Agreement to implement
    1. Carry out the plan to implement.
    2. Ensure the Go Live Acceptance Criteria are met.
    3. Complete the system implementation.
  • System available for Users

By this stage, there will be a detailed plan of the work to be undertaken and a fallback position in terms of a Roll Back Plan. The work can proceed and if something triggers the Roll Back Plan, then the Go Live aborted. As various components are delivered, they can be checked as the next component is put in place. There are likely to be unforeseen problems and resources should will be on standby to fix the problems as they occur.

It is useful to make regular reports to the Sponsor of progress. One technique is to have a schedule of phone calls to update the Sponsor on progress. If there are many people who will be interested in progress, consider use of a recorded message to update interested parties. There are telcos who provide this service for a small amount of money. It can save the project team repeating the same thing to a large number of people.

Also arrange some central information source that can be regularly updated with progress. It might be a white board or an Intranet page. It will allow everyone to see what steps are complete and how the implementation is progressing against the plan. As issues are identified, they can be logged on the information source and as they are rectified, removed.

If you do finish ahead of schedule, take the bonus time to do more testing. Better to find problems during the implementation rather than when users start using the system. Make sure things like access and security are working correctly. Check speed of the system. Ensure printers work as expected. All this testing will lessen the risk of a negative first impression.


Return to the top