The go-live date is a fixed target you don’t want to miss. Therefore the plan must contain all the details needed to make it. Preparation of the launch must be started well in advance before the actual launch so there is enough time to consider all the different elements and put the puzzle together.

Defining the cut-over approach (how to deploy the solution to the production environment), and migration approach (how to move data from one system to another), is often a complex task that needs a lot of consideration and detailed preparation. 

During the go-live process key prerequisites must be in place. This include infrastructural prerequisites like ordering new servers, firewall openings, certificates etc. 

Staffing must be in place – key resources must be in place when needed. For critical key resources substitutes can be appointed and in key tasks documented to a level where others can perform them if needed.

The launch is an important bridge between finalization of the development process often with last minute fixes and decisions on the one hand, and on the other hand a new phase in the project where real users will start to use the new solution in real life.

Making sure end-users are prepared and have realistic expectations is a core task. This include preparing end-users and other stakeholders for the obstacles and bumps on the road that is often the reality when something new is launched.

The successful launch is often determined by the ability to prioritize and handle issues quickly when they arise, and to communicate clearly to end-users about the actions that are made. Special hyper-care processes ensure that the project is prepared to provide required support until hand-over to normal operations can be made.