5.3.2 The technical change management process Flashcards

1
Q

State:

Purpose of technical change

A

Replace or upgrade technology for a business benefit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Explain:

Who, within a business, will deal with any requests for change

A

CAB - Change Advisory Board
* Responsible for assessing any potential IT changes
* Technical, decision-making staff, sometimes subject specialists will be on the panel

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

State:

4 responsibilities of the Change Advisory Board (CAB)

CAB - Change Advisory Board

A

4 of:
* Assessing any potential IT changes (main one)
* Manage quality standards
* Change requests and prioritise requests when necessary
* Review any impact on security or compliance with legislation etc.
* Monitor the process of change to understand
* Provide feedback and create documentation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Fill The Blank:

If a request for change is ………………. the planning and scheduling for the change takes place to ensure all ……………….. and ……………………….. (hardware, time, workforce) are in place to be used.

CAB - Change Advisory Board

A

Approved, Finances, Resources

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Fill The Blank:

When planning, the CAB will also ensure that the business can still ……………… while the …………. is taking place and how to mitigate any potential ……………

CAB - Change Advisory Board

A

Function, Change, Risks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Fill The Blank:

After planning, the digital change is …………………. and …………………….. while also testing the is working as intended and it does not impact other ………………..

CAB - Change Advisory Board

A

Implemented, Documented, Processes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Explain:

Briefly, Standard Technical Change Management

A

Known changes to services and/or IT system infrastructure with low risks and impacts on business; pre-approved by senior management

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Explain:

Briefly, Normal Technical Change Management

A

Changes that have to be approved prior to being carried out with high risk and must be approved via CAB - may have an impact on the business’ ability to function

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Explain:

Briefly, Emergency Technical Change Management

A

Critical changes that must be carried out as a matter of urgency - cannot be planned for

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Fill The Blank:

Identify the intended changes and the …………… behind the changes as well as ……. and anticipated timescales

Identifying the changes to be made

A

Reasons, Risks

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Fill The Blanks:

The risks involved must be communicated ………….. and timely to all relevant ………………..

Identifying, communicating potent. risks, wanted impacts to stakeholders

A

Positively, Stakeholders

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Fill The Blank:

All stakeholders must be ……………….. any changes will not cause too much ………………. to them.

Identifying, communicating potent. risks, wanted impacts to stakeholders

A

Confident, Disruption

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Fill The Blank:

Any planning of changes must be ……………….. so people carrying out changes can implement them in the correct ……….. using the correct ……………….. etc.

Configuration of the new system and process

A

Documented, Order, Equipment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Fill The Blank:

All changes must be …………… to ensure that systems and processes work as ………………..

Configuration of the new system and process

A

Tested, Intended

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Explain:

Briefly, direct changeover

Methods of implementing change

A

Major change launched all at once as opposed to more conservative approaches

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

State:

2 advantages of direct changeover

Methods of implementing change

A
  • Low cost/Cheap
  • Only one system running at a time
17
Q

State:

2 disadvantages of direct changeover

Methods of implementing change

A

2 of:
* Staff require training or may be slow to pickup the system at first without training
* Data can be lost permanently
* Difficult to plan

18
Q

Explain:

Briefly, Parallel changeover

Methods of implementing change

A

Old and new system run simulatenously until new system is ready to be fully adopted

19
Q

State:

2 advantages of parallel changeover

Methods of implementing change

A
  • Staff will be less overwhelmed by being given time to adjust
  • If new system fails, old one still available
20
Q

State:

1 disadvantage of parallel changeover

Methods of implementing change

A

Costly; have to pay for both to run + staff

21
Q

Explain:

Briefly, Pilot changeover

Methods of implementing change

A

Testing a new system within a department or office before fully rolling it out to the whole company

22
Q

State:

2 advantages of pilot changeover

Methods of implementing change

A
  • System will be working correctly when rolled out to all users
  • Allows for continuing development/changes, based off feedback
23
Q

State:

2 disadvantages of pilot changeover

Methods of implementing change

A
  • Takes a lot of time to be carried out
  • Partaking in changeover pilot (the department/region) risks loss of data
24
Q

Explain:

Briefly, Phased changeover

Methods of implementing change

A

Change from old to new system in stages to ensure all necessary fixes can be made during the changeover

25
Q

State:

2 advantages of phased changeover

Methods of implementing change

A
  • Staff can be trained gradually with only current part of system
  • Easier to find system errors
26
Q

State:

2 disadvantages of phased changeover

Methods of implementing change

A
  • More expensive than direct changeover as you have to test each phase seperately
  • Takes a long time to implement whole system