Introducing software after big bang: Fast and smashing

The big bang method is one of the best-known software rollout strategies. In the big bang strategy, all software modules are activated for all users on a specific date. From this point in time (milestone), the new software replaces the legacy system holistically, so that users do not have to maintain processes in the new and legacy systems in parallel. Big Bang is the fastest and most cost-effective implementation strategy for large companies, because there is no need to pay for, maintain and interface multiple applications in parallel - provided everything goes according to plan.

With the Big Bang implementation strategy, precise planning is very important and decisive for the success of the implementation project. If problems occur, a Big Bang implementation quickly causes high costs. In the worst case scenario, if the implementation project is aborted and fails, it is not possible to "roll back" to the legacy system and all business processes come to a standstill.

The abrupt change to a new solution can be too much for many employees - acceptance problems arise. In the worst case, the new software is not accepted and the intended goal is not achieved. Therefore, it is already of great importance to pay attention to intuitive usability when selecting the software. The introduction of complex enterprise software causes problems especially if a company has not used similar software before. If different software solutions were used before, which are now to be replaced by an ERP system, the migration of the data often causes problems.

A preparatory phase is particularly important in a software implementation using the big bang method in order to minimize the high risks of the big bang implementation strategy. The technical system administrators and key users (key users/champions) must be trained in advance by the software provider's user consultants. In addition, the new software must be subjected to extensive testing in advance, with as much real data as possible. The software provider already develops all the necessary interfaces during the preparatory phase.

In addition to software introduction according to the big bang method, purely iterative procedures, i.e. step-by-step introduction strategies and combinations of big bang approach with iterative strategies, are also possible, which may be more suitable for introduction projects in companies in individual cases.

Purely iterative approaches include:

Combined strategies are particularly suitable for very large implementation projects and offer the advantage that they can be better adapted to the individual needs and requirements of the company. This can sometimes shorten introduction times or increase acceptance of the software introduction. The risks of software introduction after Big Bang are not reduced thereby however in all cases.

Two most common combinations of iterative models with the Big Bang strategy are the following:

• Big Bang followed by functional iterative rollout: the software is introduced without preparatory agreements on the changing processes after Big Bang. The adjustments are made afterwards.
• Regional iterative introduction followed by Big Bang: First, the software is introduced step by step across the sites or departments. As soon as enough experience has been gained and the problems encountered have been solved, the software is introduced in the remaining locations according to Big Bang.

The big bang method is a fast and cost-effective way to introduce a new software system by activating all software modules at a defined point in time. However, the introduction requires thorough planning to minimize risks such as problems with acceptance, higher costs and interruptions to business processes. Intuitive usability of the new software, training of key users and tests with real data are important prerequisites for the success of a Big Bang introduction.

The advantages of the Big Bang approach include rapid implementation, manageable costs and avoidance of compatibility issues, while potential disadvantages include higher risks, greater impact on business operations and less flexibility. The decision as to whether the Big Bang method is suitable for a software implementation project depends on the complexity of the software, the size of the company and, above all, the experience of the project manager and the project team.