From the course: Putting ITIL® into Practice: Change Enablement
Unlock this course with a free trial
Join today to access over 24,800 courses taught by industry experts.
Where and when to use a request for change
From the course: Putting ITIL® into Practice: Change Enablement
Where and when to use a request for change
- [Narrator] Before updating critical systems, an RFC helps you ensure compatibility, risk assessment, and rollback plans are in place. Operating systems, databases and enterprise apps need thorough evaluation before deployment. Without an RFC, your major system upgrade might turn into a major disaster. Patching is critical, but not every patch or combination of patches is safe. An RFC verifies urgency, helps ensure impact is tested and deployment is scheduled to avoid breaking other services. Why use RFCs? Because a security fix should close a hole, not open one. Launching a new app, cloud service, or customer portal? An RFC helps ensure your work aligns with business needs, can be done with available resources and is technically feasible. Without it, all strategy changes can be made, costs can spiral, integrations can fail, and users can suffer. Firewalls, routers, VPNs, one wrong change can cut off users or expose data. An RFC documents risks, dependencies and fallback options so…