15.01.2024 Views

CompTIA A+ Certification All-in-One Exam Guide

  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Change Management Processes

A change management process enables organizations to implement changes

to IT infrastructure in a safe and cost-effective manner. There’s no single

guide to change management, though most organizations follow commonsense

guidelines. Here’s an outline of the best practices CompTIA

recommends:

• Consult documented business processes.

• Determine the purpose of the change.

• Analyze the scope of the change.

• Analyze risk involved in making (or not making) the change.

• Plan for the change.

• Educate end users about the need, benefit, and cost of the change.

• Create a dedicated team to manage the change.

• Have a backout plan in place in case the change creates negative

consequences.

• Document everything thoroughly.

Implementing Change (Scenario)

Any organization with a change management process is going to have their

own specific method to enact changes that should manifest as clearly

documented business processes. One of your first jobs as a tech is to consult

these documents so that—when change comes your way (either from you or

from on high)—you’ll already understand the processes. When it’s time for a

change, start by reviewing these documented business practices to avoid

being embarrassed for missing some important step.

Here’s a typical scenario to use for examples of managing change. Jamie

at Bayland Widgets Corp. wants to upgrade 16 systems in the design lab from

Windows 7 to Windows 10. Users are clamoring for the newer OS.

Purpose of the Change

No organization is ever going to give you new equipment or allow you to

make upgrades without knowing why they are needed. To propose a change,

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!