The introduction of new software follows a structured process that is divided into several phases. Depending on the size of the company, the software solution and the specific requirements, the individual steps may vary, but the basic process often remains the same. The following describes a typical procedure for implementing new software, from planning, configuration and testing to training and the final go-live.

Step 1: The kick-off

At the beginning of the project, all relevant stakeholders are invited to a kick-off workshop. During this workshop, the objectives of the project are presented and the milestones and timetables for the next phases are defined. This step lays the foundation for the specifications, which describe the requirements and objectives of the project in detail.

Step 2: The conception

In the conception phase, detailed requirements and system adjustments are developed. These are recorded in the specifications and form the basis for the implementation. The client must accept the specifications before the implementation begins.

Step 3: Implementation

The implementation phase is crucial because this is where the functionalities developed in the specifications are realized. This includes configuring the software in line with organizational requirements and customizing it to the company’s specific needs.

Step 4: Testing and quality assurance

After implementation, the software is tested in a test environment for functionality and quality. All use cases defined in the specifications serve as a basis for testing. After successful testing, the productive environment is set up, which represents the finished, customized software.

Step 5: Training

Comprehensive training for end users is crucial for the success of the software implementation. The training goes beyond the general use of the software and also includes subject-specific processes that help users to take full advantage of the software.

Step 6: Go-live

The go-live marks the final step. There are two common approaches:

The big bang: All users switch to the new system at the same time. This method is well suited for smaller companies with less complex requirements.

The phased approach: The go-live takes place gradually, by user group or location. This method is suitable for larger companies with more complex projects and many users.