5.3.2. Change managemet process

• Change management process starts with the submission of a request for change (RFC)
• A RFC form will generally include additional info such as the scope of the change, required resources, and objectives of the change
• A change can be broken down into 4 parts these are?

  Identify changes to be made

  Request changes be made

  Communicate change impact to stakeholders

  Configure new system
• To choose what to do regarding an RFC generally potential risks and impacts on stakeholders are considered, if we decide to go through with a change the impacts are to be communicated.
• Once a RFC has been approved we must configure the new system or process. This often include testing the new system or process to ensure it is functioning properly and will work with any pre-existing systems.
• Parallel implementing change, whilst maintaining the existing system, running them both together
• Parallel is used when change must be implemented quickly and allows quick reversion
• Direct change is implementing the change as a single unit, with no testing etc.
• Direct is used when change will have little impact and allows very quick changes, however there is no testing
• Phased is implementing the change in stages -known as phases. Each phase is large and complex, allowing for testing
• PHased change is used when a change needs to be tested before being implemented
• Pilot often allows for tech ambassadors, where the few individiduals who had used it in the small controlled environment can be used to teach other
• PIlot is used when the change is a big change that is best tested in a seperate environment and used normally
• Pilot change is implementing change into a small, controlled environment generally with few employees
• dirpil parpha is a pneumonic to remember

  DIRect

  PILot

  PARallel

  PHAsed
• Pneumonic to remember methods of implementing change?

  DIRPIL PARPHA