6. Direct implementation

With this approach, the system is implemented and tested to ensure it performs properly. Then the old system is removed and the new one put in its place without any overlap or limited roll out.

direct implementation

This is a risky strategy as any issues with the new system may have an immediate impact on the day to day activity of the organisation.

On the other hand it has the advantage of being a fast roll-out compared to the parallel, phased or pilot approaches.

This is a good choice when

  1. The system is not critical to the organisation, so if it has a problem, it will not be too serious.
  2. There is high confidence that the system will work first time

The key to using the direct approach is very careful project planning. For example, there will be thorough technical development, a comprehensive test schedule, robust training regime and so on. So when the system goes live, it just works.


challenge see if you can find out one extra fact on this topic that we haven't already told you

Click on this link: Successful project planning for IT