Please enable JavaScript.

Coggle requires JavaScript to display documents.

Rollout Strategies - Coggle Diagram

- - - - 3.A phased rollout approach
        
        takes the parallel rollout one step further
        
        gradually
        introducing the new system in less-overwhelming
        
        bite-sized chunks of
        functionality.
        
        Although a phased rollout is preferable, business pressures to get a
        new system quickly up and running can make it less feasible
      - where the old and new system are simultaneously available to
        users for an extended period and the old one is subsequently turned off on the
        rollout date
        
        This approach provides a safety net for technology glitches
        
        However, it prolongs the rollout period and requires reconciling data from the overlapping
        period between the old system to the new system
    - - (Migration of any data from the old system must be completed before the rollout
        date.)
      - The risk is that any bugs or glitches in the system can have a widespread
        impact.
      - Technology glitches often lurk even if completed projects are pilot tested
        with a small group of actual users
      - Direct cutover is appropriate if the old system
        is unusable and if the new system is not mission critical to your firm’s core
        operations