Change request management isn’t the same as change management. It’s a means of keeping track of the various change requests that come in from around the company after a major system implementation. You need a way to track these requests, regardless of what they are. For large issues, you may want to open a new project, but for small ones you just need a way to track the fix. That’s why it’s important to have a reliable, scalable methodology to manage the change requests. This article gives you a guideline for such a change request management process, and it includes several KPIs to ensure that the process remains transparent to both business and IT.
Anton Karnaukhov
Anton Karnaukhov is a senior IT manager at Pacific Coast Companies, Inc., in Sacramento, California. He earned an MBA degree at Heriot-Watt University and a BS/BA degree with a specialization in computer information systems at Western Carolina University. Anton has more than eight years of SAP implementation and development experience focusing on business intelligence and logistics modules in the manufacturing and resale industries.
You may contact the author at anton.karnaukhov@paccoast.com.
If you have comments about this article or publication, or would like to submit an article idea, please contact the editor.
