"Day in the Life" Demonstration

IT Change Manager

<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 >>

Change Management Roles

The second tab is where you configure the user roles and service groups. To begin using Giva eChangeManager, first you must set up roles. These are the duties that people have in the change management process. Giva eChangeManager follows IT Infrastructure Library® (ITIL®) requirements when defining Giva eChangeManager roles:

After you define the user/customer role, you define the service group. For purposes of Giva eChangeManager, simply check the Enable box for the appropriate service group. If the user is a member of more than one service group, indicate the primary group by checking the "Default" circle. Service groups receive automatic notifications at various stages of the RFC life cycle.

Definitions:

CAB – Change Advisory Board.

EC – Emergency Committee.

User –  A user creates new Request for Change (RFC) records, is assigned as a change implementer, is assigned as change builder, or is an independent change plan tester

Manager –  The Change Manager, the one person responsible for administrating the change management process. Best practice says to assign only one person the role of Change Manager. According to the ITIL® definition, the Change Manager is responsible for compliance to the Change Management processes. The Change Manager unilaterally approves low-risk changes, informs the CAB/EC of riskier new changes needing discussion and approval and is responsible for publishing the Forward Schedule of Changes (FSC).

Advisory Board –  This role is for people who sit on the Change Advisory Board (CAB). According to the ITIL® definition, the Change Advisory Board is responsible for the review of all submitted Requests for Change. Change Advisory Board members are senior staff responsible for attending all relevant Change Advisory Board meetings and, when required, CAB Emergency Committee meetings. The function of the CAB members is to advise the Change Manager of the appropriate action to take.

Emergency Committee –  This role is for people who sit on the Emergency Committee (EC). Best practices say that the EC members are senior executives such as the CIO, CFO, and COO. They approve top priority (URGENT), risky changes that must happen without the benefits of a detailed Implementation, Testing, or Backout Plans because the consequences of delaying will cause major harm to the business. According to the ITIL® definition, the Emergency Committee is a subset of the Change Advisory Board capable of making impact assessments in urgent circumstances.

Administrator –  This role is for the people responsible for configuring Giva eChangeManager. They perform such duties as defining all menu items and assigning roles. Giva recommends that you only have a small number of Administrators. Ideally, we recommend that you have only two Administrators. One person should be the main person responsible for Giva administration and the other person should be a backup.

<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 >>