A fomer colleague in the UAE asked me for a Change Request Process and Template yesterday. I sent him a change CR log too. By putting a change process in place, you can easily monitor and control the amount of change that takes place, providing the process provides each of the key steps for managing change within projects are included.
I know this all sounds like basic stuff, but you’d be amazed how many high profile, high budget projects are running without change management. I’ve seen it!
By implementing a Change Management Process, you will be able to:
- Identify the requirements for change within your project
- Put in place a process for submitting Change Requests
- Determine the feasibility of changes requested
- Formally approve each change before they occur
- Schedule change to happen, when you want it to happen
- Review the impact of each change on your project
Change Management is a core Project Management function, and it’s critical to achieving success because change usually affects your ability to deliver your project within scope, therefore increasing your costs and delivery timeframes.
To properly control project scope, you should use a well thought through Change Management Process. It will give you a near little tool for managing change effortlessly within your projects.
1 response so far ↓
Ammar // 5 January 2007 at 5:50 pm |
I agree with Robert on this (as well as I am sure anybody who has gone through complex projects)… This also allow the project manager to detect scope creep!… Without formal change order approval, it is easy for the project manager to see major transformation of the scope of a project.