Change Management Process Implementation Suggestions


Change Management is first and foremost a process. It is a process involving all of IT. It must have the highest management support. The following are roles and responsibilities that need to be in place before embarking on a Change Management process. These must be in place before a change management process can be successfully implemented.  Consider SaaS (Software-as-a-Service) to make getting up and running faster, easier and less expensive.

  • Change Manager
    • Ensures the Change Process Is Followed
    • Approves Low Risk Changes
    • Issues Future Forward Schedule of Changes (FSC)
    • Coordinates Change Building
    • Reviews All Implemented Changes
    • Closes Change Records
    • Produces Management Reports
  • Change Advisory Board (CAB)
    • Reviews All Submitted Request for Changes (RFC)
    • Attends Relevant CAB or CAB/EC Meetings
    • Advises the Change Manger
  • Emergency Committee (EC) (Subset of the CAB)
    • Makes Decisions on Urgent Changes

Please see for more information.

Client Success

  • 50% reduction in time to deploy Giva's change, incident, problem, asset management and knowledgebase modules
  • 60% reduction in the 5 year Total Cost of Ownership (TCO)
  • Saved at least 1 FTE due to lower ongoing administration
  • Saved 1 week per month due to easy to use reports
  • Increased to 90% achievement in meeting service level agreements
  • 70% reduction in generating reports and admin; eliminated 35 hours/month
  • 50% faster to create/assign a service request
  • 60% increase in information captured during the initial phone call
  • 50% increase in the number of service requests created due to intuitive design
  • 80% increase in productivity by using Giva's dashboards and reports
  • 60% increase in meeting service level agreements
  • 45% increase in the number of the calls logged due to Giva's intuitiveness and ease of use
  • 50% increase in productivity by using Giva's integrated custom forms