Change management на собеседовании системного аналитика

ITIL change types

Standard. Pre-approved, low-risk, repeatable. Auto-approve.

Normal. Goes через approval process.

Emergency. Hot fix. Expedited approval.

Change request

Formal document.

• What changing.
• Why.
• Risk assessment.
• Rollback plan.
• Testing performed.
• Stakeholders affected.

В strict environments (banks) — required для каждое production change.

CAB

Change Advisory Board. Group reviewing changes.

Composition. Tech leads, ops, security, business reps.

Frequency. Weekly typically. Emergency CAB ad-hoc.

Critique. Slow processes. Modern DevOps moves к auto-approve standard changes.

Risk assessment

Evaluate change impact:

• Affected services.
• Estimated downtime / disruption.
• Rollback feasibility.
• Customer impact.

Risk score → approval level needed.

Modern (DevOps)

Traditional ITIL — slow.

DevOps replaces:

• Standard changes — fully automated.
• Pre-approved playbooks.
• Continuous deployment.
• Post-deploy review (instead pre-approval).

В regulated industries (banks, медицина) — мixed: ITIL для high-risk, DevOps для low.

Связанные темы

• SDLC модели для SA
• CI/CD pipelines для SA
• Stakeholder analysis для SA
• Incident response для SA
• Подготовка к собесу системного аналитика

FAQ

Это официальная информация?

Нет. Статья основана на ITIL framework и DevOps practices.

Тренируйте системный анализ — откройте тренажёр с 1500+ вопросами для собесов.