Differences between Configuration Management and Change Management is another topic that often confuses many PMP Certificate aspirants; therefore, in this blog post I’m going to explain this topic to you. I hope after reading this blog post, you wouldn’t have any doubt.
Let’s start with an example:
Suppose you are constructing a two story school building for a client. Everything is going as planned. Suddenly the client comes to you and asks to make the school building into a three story instead of two story.
Hmmm…
So, what you will do now? He asked you to change the design of the building (your project’s product).
Of course, you will re-plan and reschedule it; moreover, you also need to change your budget and get it approved.
Hence, you will raise a change request including all these changes and will try to get it approved as soon as possible.
These changes in product configuration will be handled under Configuration Management because here the configuration of your school building is changed. Earlier it was a two story building, and now it is a three story.
Now, let’s move to Change Management.
You are constructing the same school building. Suddenly your contractor for steel works runs away, and you are struggling to find a new contractor. After a lot of searching you find a contractor for steel works but he won’t start working for your project for one week. This will delay your project end date by one week. Hence, you will raise a change request to reschedule your schedule baseline and will try to get approval for it.
Note that, here also you raised a change request, but this request was to increase the deadline of project by one week. There is no change in your product (change required only in schedule baseline); i.e. school building will be same; though, you will handover this building to client one week late.
This change in project process will be handled under the Change Management because here the configuration of your school building is unchanged. Earlier it was a two story building, and now it is still a two story building.
Summary:
- In Configuration Management, changes related to product’s characteristics are managed.
- Change Management manages the changes in project baselines or processes.
I hope now you wouldn’t have any problem to crack question on the PMP Certification exam from this topic.
Hi Fahad,
Can we say Configuration management is scope change and change management is shcedule change?
Thanks
Ramesh
Configuration management is scope change – Yes, we can say this.
And Change Management includes the change in schedule and cost baselines.
But in some questions asked where would you go to find a document, the answer is config management. seems its considered as a document management repository tool also, right ?
There it talks about the latest version of the documents … Becoz we have changes to the baseline when there is an approved change request.
Hello Shweta,
Did Sangeetha give you the answer? If not, then could you be little more specific?
Excellent Clarifications…. Difficult to forget now…Thanks…
You’re welcome.
Dear Fahad,
Keep on explaining the things like your way!!
Thanks for your comments Ritesh.
Awesome. Thanks a lot for your amazing explanation
You are welcome.
Fahad,
Your explanation about the difference between change and configuration management is valid. I would like to add that Configuration Management also includes managing changes to the documentations ( to enable the project team know which version is current) and the organisation tool employed in this effort.
Regards,
Shariff
Hi Shariff,
Excellent explanation with good example. Thanks. Can you also explain different between change management system and configuration management system.
Hi Thathish,
To my understanding, both configuration and change management systems are component of the organisation project management information system. However, the configuration management system consists of documented procedures employ in identifying, documenting and controlling changes to functional and physical characteristics of a product, service and results, including tracking system and approval level. On the other hand, a change management system defines how project deliverables and documentation is controlled, changed and approved. The latter is usually a subset of the former. See PMBOK Guide page 428-429.
I hope this clarification helps.
thank you very much Fahad