E-mail
Change Management - To each their own
Geoff Halprin
Abstract
The only way to ensure the integrity of a production computing environment is through a formal Change Management process. But anyone who's worked at a large facility can tell you horror stories about having to wait 60 days to reboot a machine, and other complete failures of Change Management processes.
Get it wrong and the resuts are, well, bad:
- Slow moving systems that can't keep pace with the business.
- Systems with uptime figures below 97%.
- Unhappy web customers moving to a competitor's site.
- Unhappy internal customers looking to outsource IT.
- Lost productivity costing tens of thousands of dollars an hour.
And the obvious cost:
- Lost sysadmin productivity while they cool their heels in meetings, writing up forms, and waiting just to do their jobs.
This tutorial looks at Change Management, from principles to implementation. We look at what should be in a CM process, and how to tune the process to meet your business' requirements.
Who should attend?
System administrators who wish to learn how to better manage change and risk, and become more professional in their system management practices.
System administrators who are responsible for developing or managing their organisation's Change Management process, or who are hoping to influence and improve their organisation's process.