Change Management
Summary
PDF p.374Change management involves planning, trialing, and implementing changes with rollback plans to minimize negative impacts. It includes scheduling changes to avoid workflow disruptions.
In plain words
Supplementary — not from your PDFChange management (as a policy area) plans, trials and implements changes with rollback plans, scheduling them to avoid disrupting workflows. It considers dependent components before making a change.
Detailed explanation
PDF p.374-
Process
- Planning: Consider dependent components.
- Trialing: Test significant changes.
- Rollback Plans: Reverse harmful changes.
- Scheduling: Avoid workflow disruptions.
Important terms
taken from the text above- Planning
- Consider dependent components.
- Trialing
- Test significant changes.
- Rollback Plans
- Reverse harmful changes.
- Scheduling
- Avoid workflow disruptions.
Examples & real-world scenarios
Supplementary — not from your PDF- Testing a change in a lab before production.
- A rollback plan ready before applying an update.
- Scheduling a change for a maintenance window.
Scenario
An untested firewall change breaks a business app during peak hours. Trialing it first and scheduling it for off-peak, with a rollback plan, would have avoided the outage.
Common mistakes
Supplementary — not from your PDF- Making changes with no rollback plan.
- Scheduling changes during business-critical hours.
Practical skills
Supplementary — not from your PDF- List the stages of a managed change.
What I should remember
Key Points PDF p.374- Planning: Consider dependencies.
- Trialing: Test changes.
- Rollback Plans: Reverse changes.
- Scheduling: Avoid disruptions.