Getting the implementation phase right the first time is crucial for any project manager or project team. The method used for implementing a new solution to replace the old solution can vary depending on the needs of the customer and the actual flow of the system itself.
In his book, “Project Management Nation” Jason Charvat discusses three types of implementation approaches: Parallel Implementation, Phased Implementation, and Crash Implementation. Read on as Mr. Charvat discusses each type of implementation in further detail.
Implementation Approaches
There are a variety of options that a project manager could consider when implementing a solution. There are advantages and disadvantages to each type, and the choice usually depends on the client organizational setup and the complexity of the solution to be implemented.
For example, an international client with multiple offices needs to upgrade a certain e-mail system in all offices by a certain “go-live” date. In such a scenario, a project manager is faced with huge logistical and technical challenges, and the implementation strategy is pivotal in deciding on the rollout.
These implementation choices available to a project manager are:
- Parallel implementation
- Phased implementation
- Crash implementation
Parallel Implementation
A parallel implementation or approach implies that a new solution is implemented parallel to the current operating system in use. Those who are using the system will not see major downtime once it is implemented. The trick here is to implement the system.
Once the new solution is tested and up and running, it is “switched” on and the older version is “switched” off. The advantages with a parallel implementation include (1) less disruption to the business, and (2) no loss of business if the new system suddenly fails.
Phase Approach
Sometimes trying to implement a solution all at once is not feasible because many clients have essential operations that run during normal working hours and cannot afford the luxury of having their entire operation close down for a lengthy period in time.
Often, clients have front office staff that attend to these operations (such as call centres, help desks, etc.), and they work in 24-hour shifts. This is why many clients approve of a phased implementation approach, and the project team must ensure that the phased implementation is possible. This approach involves implementing the solution to a certain amount of users and then rolling them onto the new solution, while the rest of the users are rolled out in a similar fashion until the entire solution is rolled out within the client environment.
The phase approach works well because (1) there is minimal disruption to the client's operation, and (2) problems are resolved quickly. The phased approach could also be used if there is more than one department. The project manager could decide that implementing the solution in one department at a time could be more reliable than trying to roll out all departments at the same time.
Crash Implementation
Careful planning needs to take place when considering a crash (also known as full-blown) implementation. It takes an incredible amount of planning and re-planning to ensure no problems arise. In fact, with this type of implementation, the necessary contingencies need to be prepared and reviewed well in advance of the actual implementation, in order to minimize any potential failure.
The necessary IT support staff also need to be available on the chosen implementation period. A full-blown implementation should be scheduled to take place over a slow period, such as a holiday or weekend.