Question

Difficulty: EasyChange Management Processes

An IT technician is preparing to update software on corporate workstations following organizational policy. In what order should the technician execute the stages of the standard change management process?

  1. 1Define the purpose and scope of the proposed change.
  2. 2Perform a risk analysis and draft a comprehensive rollback plan.
  3. 3Submit the change request to the Change Advisory Board (CAB) for authorization.
  4. 4Notify affected end users of the scheduled maintenance window.
  5. 5Implement the change and execute post-implementation testing.

Answer

The proper chronological sequence of the change management lifecycle is: 1) Define the purpose and scope of the proposed change, 2) Perform a risk analysis and draft a comprehensive rollback plan, 3) Submit the change request to the Change Advisory Board (CAB) for authorization, 4) Notify affected end users of the scheduled maintenance window, and 5) Implement the change and execute post-implementation testing.
The standard CompTIA change management workflow dictates defining purpose and scope first, followed by performing risk analysis and preparing a rollback plan. Next, formal authorization must be granted by the Change Advisory Board (CAB). Once authorized, end users are notified, and lastly, the change is implemented and verified through post-implementation testing.

Step-by-Step Solution

1
Identify parameters of the change
The purpose and scope are clearly defined.
Understanding what is being changed and why is necessary before evaluating potential impacts.
2
Evaluate impact and plan for recovery
Risks are documented and a rollback strategy is created.
Board review requires knowing potential risks and having a strategy to revert if deployment fails.
3
Seek governance approval
The Change Advisory Board (CAB) reviews and approves the request.
Changes to production systems require authorization to ensure alignment with business needs and security.
4
Inform stakeholders
Users are alerted to potential service disruption and timeframes.
Timely notifications allow business units to prepare for planned outages.
5
Deploy and validate
The change is applied and confirmed functional via testing.
Post-implementation testing verifies that the change achieved its goal without breaking services.

Key Concept

Standard Change Management Lifecycle
Rate this question