FLASH CARDS

9.02 Explain basic change-management best practices

  • What is the primary goal of change management?

  • To reduce the risk of service disruptions caused by configuration changes.

  • What does ITIL stand for?

  • Information Technology (IT) Infrastructure Library.

  • What are the four key elements of ITIL's configuration management model?

  • (a) Service Assets, (b) Configuration Items (CIs): Assets that require management to deliver services, (c) Configuration Baselines: Predefined settings for secure, reliable operation, and (d) Performance Baselines: Metrics used to monitor the ongoing performance of a CI.

  • What is a Configuration Item (CI)?

  • A specific asset that requires management procedures to deliver IT services, such as servers, software, or networking equipment.

  • What is a configuration baseline?

  • Predefined settings and configurations applied to ensure the secure and reliable operation of a Configuration Item (CI).

  • What is a change request?

  • A formal proposal to fix an issue, accommodate a new business need, or improve an existing process or system.

  • What are the two types of change requests?

  • (a) Reactive changes: Forced by external factors (e.g., fixing outages or security vulnerabilities), and (b) Proactive changes: Initiated internally to anticipate future needs (e.g., system upgrades).

  • What is a Request for Change (RFC)?

  • A formal document submitted to propose a change, outlining the business case, risks, benefits, and steps for implementation.

  • What are the main components of an RFC (Request for Change)?

  • (a) Purpose of the Change, (b) Scope of the Change, (c) Risk Analysis, and (d) Success Criteria

  • What is the role of a Change Advisory Board (CAB)?

  • To review, assess, and approve major changes, considering both business and technical aspects.

  • Who are typically included in a Change Advisory Board (CAB)?

  • (a) Stakeholders affected by the change, (b) Technicians responsible for implementing the change, and (c) Managers/directors who can approve the budget.

  • What is risk analysis in change management?

  • A process to evaluate the potential problems and benefits associated with a proposed change.

  • What are the two types of risk analysis?

  • (a) Quantitative Risk Analysis: Uses measurable values to assess risk, and (b) Qualitative Risk Analysis: Based on informed opinions and past experiences.

  • What does a traffic light system in risk analysis represent?

  • (a) Red: High risk, (b) Orange: Moderate risk, and (c) Green: Minimal risk

  • What is a rollback plan?

  • A backup plan to revert the system to its previous state in case the change causes problems.

  • Why is testing a change important before implementing it?

  • It helps identify potential issues in a controlled, isolated environment (sandbox) before applying the change to a live system.

  • What is a sandbox environment?

  • A testing environment that replicates the production system but is isolated from it, used for testing changes before live implementation.

  • What should be done to minimize downtime during significant changes?

  • The change should be applied during a scheduled maintenance window, and stakeholders should be notified in advance.

  • Why is end-user acceptance important in change management?

  • It ensures that users are comfortable with the change, can adapt to new systems, and can provide feedback to improve the change process.

  • What are the three strategies for managing end-user acceptance?

  • (a) Involving end-user representatives in the CAB, (b) Conducting User Acceptance Testing (UAT), and (c) Providing training and support materials before the change.

  • What is the purpose of User Acceptance Testing (UAT)?

  • To allow end-users to test the updated system and provide feedback before full implementation.

  • What are proactive changes in an IT environment?

  • Changes initiated internally in anticipation of future needs, such as planned system upgrades or process improvements.

  • What is the purpose of RFC documentation?

  • To provide a formal record of the change, risks, benefits, and steps for implementation, ensuring transparency and accountability.

  • What is the significance of having a rollback plan in place during a change?

  • It allows for the system to be reverted to its previous state if the change causes unintended issues, minimizing service disruption.

  • How can stakeholders be notified of a scheduled change?

  • Through internal communication systems, including emails, notices, and notifications, to prepare them for potential impacts like downtime.