Study 5 IT Change Management with 12 free online flashcards. Review key terms, definitions, and concepts with this interactive flashcard deck.
What is IT change management?
IT change management is the controlled process of modifying technology services, systems, configurations, or related procedures to deliver useful changes while limiting disruption, security exposure, and operational risk.
What defines a standard change?
A standard change is routine and low risk, and follows a documented, preapproved procedure. Record and perform each instance according to that procedure.
Which factors should a change assessment consider?
Assess the change’s purpose, affected systems and users, dependencies, timing, and potential effects on availability, security, privacy, safety, and compliance.
How should review effort relate to change risk?
Estimate the likelihood and impact of failure, identify mitigations, and make the level of review proportionate to the change’s risk and impact.
What purpose and scope should a change request state?
A request should state the reason for the change, its intended result, and the systems, services, configurations, and people affected.
Who should approve a normal change?
Before implementing a normal change, obtain approval from people authorized by organizational policy. Record the decision and its rationale.
What should change communications tell affected stakeholders?
Tell affected people what is changing, why and when, what effects or actions to expect, and where to get help. Give notice early enough to prepare while protecting sensitive operational details.
What should be confirmed before implementing a change?
Before implementation, confirm authorization, scope, timing, access, dependencies, backups or saved configurations, and rollback readiness.
What should happen when post-change validation fails?
Verify that the change achieved its intended result and that affected services remain secure and operational. If validation fails, follow the rollback plan or escalate through incident procedures.
What must be recorded before closing a change?
Close the record only after documenting what and when work was done, who performed and approved it, validation results, unexpected effects, and rollback or follow-up work.
What approval does a normal change require?
A normal change requires case-by-case assessment and approval before implementation.
How should an emergency change be handled?
An emergency change addresses an active outage, security threat, or similarly time-critical risk. Use the emergency authorization process and complete required documentation and review afterward.