Project environments are dynamic, and changes are constant in areas like process, planning, or scope. You can group these changes into two categories:
- 更换管理层
- 配置管理
“Change Management” is the first category. Here you manage changes related to project management plans, processes, and baselines.
在第二类中，您管理与product scope, known as configuration management.
Change requests are required when baselines are established, and you have to make changes to them. If the baselines are not set, no formal change request is required. Change requests and configuration requests are part of the integration management system.
Change management is a well-known term in project management, but configuration management is not. In the IT field, the term ‘configuration management’ is used frequently, so if you are not in this industry, you may face issues with understanding the concept.
As a non-IT professional, I had this struggle. However, now that I have passed the PMP and PMI-RMP exams, I can help you understand the concepts in this blog post.
请注意，变更管理和配置管理是最重要的概念PMP exam，您将在上面看到许多问题。
变更管理系统
根据PMBOK指南第六版，“变更控bob手机客户端制侧重于识别，记录和控制更改the project和项目基线。”
在变更管理系统中，您可以管理与项目范围，计划和基准相关的更改。
例如，您用光了资金，需要额外的资金来完成该项目，因此，您将提出更改请求，以供额外资金。或者，您可能无法在指定的时间内完成项目，并且需要时间延长。
In the change management system, the change request is analyzed for any possible impact on any other project objectives. Afterward, the request is either approved or rejected.
To minimize disruption, a change management system must ensure that all parameters are identified and analyzed for any possible impact.
If the change request is approved, you will update the concerned baseline, update the project documents, and inform the concerned stakeholders.
更换管理层Activities
您在变更管理期间进行以下操作：
- Identify the changes.
- 为更改准备适当的文档。
- Review, analyze, and make a decision for the change request.
- 确保请求已实施，注册和传达。
配置管理System
根据PMBOK指南第6版，“配置控bob手机客户端件侧重于可交付成果和流程的规格。”
In the configuration management system, you manage the changes related to the product specification and the process.
For example, suppose you are developing a product and the client requests the addition of some extra features.
由于此更改与产品的配置有关，因此您将使用配置管理系统处理此更改。
Configuration management documents how you will monitor and control changes. It is a process of defining configurable items (product, service, result, and component) and controlling changes to such items.
The configuration management plan keeps version control of the product. Here you can keep a log of all the changes made to any version of the product for review.
配置管理Activities
You do the following during configuration management:
- Identify the configurable items.
- 记录并准备所有可配置项目的报告。
- Verify and conduct an audit of all configurations are as per the requirements.
变更和配置管理的真实世界示例
Suppose you are working on a project to construct a school building with ten classrooms.
Case: 1
During the middle of the project, your contractor for steelwork walks off the job and you have to find a replacement. You find an alternative, but the new contractor will not start working on your project for a week.
这个项目将推迟。Therefore, you will raise a change request for a one-week extension of the schedule through the change management system.
Once this request is approved, you will update your schedule baseline.
这是变更管理系统的一个示例。
现在，让我们查看配置管理系统的示例。
Case: 2
You are constructing a school building, and the client requests that you increase the number of rooms from ten to fifteen.
This is a request to change the product scope as the client has altered the product configuration.
You will handle this change under the configuration management system because here the specifications of your product have changed. Earlier, the school building had ten rooms, and now it will have fifteen rooms.
请注意，在第一种情况下，您提出了更改请求，以将项目的截止日期增加一周。产品没有变化，仅在计划基准中需要更改；教学大楼是相同的，但是一周后，您将把这座建筑物交给客户。
The Difference Between Change Management and Configuration Management Systems
The main difference between the change management and configuration management systems is that change management deals with processes, plans, and baselines, while configuration management deals with product specifications.
An example of a change management system can be additional funding requirements or a schedule extension, while an example of configuration management can be an extra feature added to the product.
Conditions for Change Management
The following are a few conditions for change management:
- Delay in schedule: You will have to develop a new schedule reflecting the current situation.
- 成本超支：您需要重新估计您的成本才能完成该项目。
配置管理条件
The following are a few conditions for configuration management:
- Market competition forces new features on the product.
- The project took so long that the product is obsolete, so an update is required.
- The client requested you add some extra functions.
- Due to cost overrun, some features are removed from the product.
- To complete the project early, some features are removed.
更换管理层Vs Configuration Management
Change management and configuration management do not compete for the same space. They are used for different purposes.
According to the PMBOK Guide 6th edition, “Configuration control is focused on the specification of both the deliverables and the processes, while change control is focused on identifying, documenting, and approving or rejecting changes to the project documents, deliverables, or baselines.”
Any change in product configuration will also affect the project scope, and you will update your project plans, cost, and schedule baselines.
Configuration management has a larger scope than change management.
谁可以提出更改和配置请求，谁可以授权？
任何人都可以提出更改请求，但必须由项目经理或更高的权威批准，如配置或变更管理计划中所述。如果客户不参与该过程，则需要他们的同意才能实施更改请求。
A higher authority can be a Change Control Board (CCB), Project Management Office (PMO), or any other stakeholder as mentioned in the project management plan.
关于配置请求通常，它来自客户端，因为它涉及产品的更改。
该请求由项目经理审查，然后转发给有关的高级权力，以供其审查和批准。可能需要客户的协议，因为他们必须支付任何其他功能。
Summary
变更管理和配置管理是集成管理的一部分，并且都涉及项目或产品中可能发生的所有更改。变更管理与与计划，过程和基准相关的更改有关，而配置管理涉及与产品范围相关的更改。项目经理的工作是提出这些请求，并确保对它们进行适当的审查。一旦做出决定，应立即实施。
Now I hope you will not have any problem in solving questions on the PMP exam regarding change management and configuration management systems.
您如何管理项目的更改？请通过评论部分分享您的经验。
Hello Fahad,
谢谢for your well thought out article.
I like your definitions, and seems correct; and certainly one way to interpret the PMBOK. But, part of the problem (and why you have written this article and folks like me and rest of your readers look for clarification), is that the PMBOK very much makes it all a fuzzy deal. Your definition is good and makes perfect sense—it’s what I’d also espoused to: Configuration has to do with Product; Change has to do with Project docs, baselines, processes, etc. But there are contradictions.
And, as I’ve tried to make sense of it in my own head in studying PMBOK (as you know PMI has “THEIR definition” of things, not always the same as “Organization/Company lambda’s”), there are some contradictions in PMBOK, and thus in your own definitions above—which are indeed direct out of PMBOK. You say that “Change Control” is about “Project stuff” — Project Documents, Baselines and Processes ; and “Configuration Control” as Product/Scope related (“Product Stuff”). Yet, you then correctly quote PMBOK that ““Configuration Control focuses on the specifications of both the deliverables and the processes” (i.e., note PROCESSES).
此外，当您引用PMBOK时，您再次指出矛盾：“配置控件专注于可交付成果和流程的规范（即注释过程！），而更改控制则集中于识别，记录和批准或批准或批准或拒绝对项目文档，可交付成果或基准的更改”（注释可交付物！）。因此，不符合您所陈述的解释 /省。
Another interpretation (that I’ve enountered) is that Change Control is the process of changing Project “Artifacts” (Project document, plans, process, deliverables, baselines – in short, everything that is under control): the written change requests, the Change Control Board, voting, approval / rejections, etc. And that Configuration control is the versioning, identification of “current version”, archiving of old versions, etc. of all “Project Artifacts” (Artifacts covering both “Project Stuff” like docs & processes and “Product Stuff”, like deliverables). This is the one espoused by Rita Mulcahey (her PM book). This interpretation also has problems and contradictions with some of the same definitions (and others) of Change Control (and Change Mgmt) and Configuration Control (and Config Mgmt) that is found in PMBOK.
All this to say: PMBOK was written by a lot of folks and then “Controlled” over its various authors and chapters to ensure overall integrity. But there remain unclarities and contradictions – and I believe this is one. They seem to clear these up with new versions of PMBOK, but others appear. All this said, your definition is a good one – and one that I have always thought was true. Now I am beginning to wonder. Having read around and now studying for PMBOK — and thus trying to understand “How does PMBOK define this” – because as stated earlier PMBOK definition is not always same one’s “real world” definition. That’s okay, it’s just not okay with they are not clear and there are contradictions in their method. Thanks. Great article. If you can or in position to dialogue with them– tell PMI to clarify their defintiions! Look forward to your feedback.
变更管理”是第一类。在这里，您可以管理与项目管理计划，{Processes}和基线有关的更改。
According to the PMBOK Guide 6th edition, “Configuration Control focuses on the specifications of both the deliverables and the {processes}.”
我不明白如何处理{process}的两个术语
请澄清一下。
Hello Anas,
Change management is a subset of configuration management.
Hi Mr. Fahad,
Now, if the client request change in my scope,
我需要并行进行变更管理和配置管理
Hello Anas,
我相信他要求更改产品范围。在这种情况下，您将进行配置管理。
Hi Fahad,
更改产品范围，不需要更改时间表和成本基线吗？随着产品范围的增加，成本和时间的增加。然后，我们必须对两个配置管理进行处理，然后进行变更管理，不是吗？
Change management is a part of configuration management.
Does the Configuration Management, lead to raise a Change request in Project Management ?
Below are same 2 examples used in here, to help you understand, what I am trying to convey.
示例1
在项目中间，我的钢铁工作承包商脱离了工作，我必须找到一个替代品。我找到了另一种选择，但是新承包商将在一个星期内开始从事该项目。
这个项目将推迟。因此,我将意大利广播电视公司se a change request for a one-week extension of the schedule through the change management system.
示例2
现在，我正在建造一座学校建筑物，客户要求我必须将房间数量从10到15增加。
This is a request to change the product scope as the client has altered the product configuration.
I will handle this change under the configuration management system because here the specifications of the product have changed. Earlier the school building had ten rooms, and now it will have fifteen rooms.
However, building additional 5 rooms will take more time than building 10 rooms, planned earlier. Hence, my schedule will also change as a result effecting my baseline, and so I have to raise a change request.
Please let me know if my understanding is correct !
在这两种情况下，您都会提出更改请求。
Very well explained. Thank you
You are welcome Harshala.
That’s a great one brother. Many thanks for making me understand these concept better in this context.
You are welcome Muhammed.
Partly wrong explanation…
Hello Tunc, what part is wrong?
Fantastic !
谢谢Babak.
很棒的解释，您清楚地指出了我在这部分的混乱。太感谢了。
You are welcome Kenny.
very useful
谢谢Shriram的评论。
谢谢。
Change management deals with project scope while Configuration management deals with product scope.
Correct.
400 questions are in simulation?
Hello Mahfuz,
In the PMP Question Bank you will find 400 Questions. The PMP Mock Test has 200 questions.
ASC Fahad, thanks in million Brother for your great and Briliant mind for providing us this wealthy knowledge,
Wasalaam Ishmael，
Thanks for your comment.
很棒的文章。配置管理对我来说是新的，您的帖子很有用。谢谢。
Anwar
Janbi.me
You are welcome Anwar.
This article is very good. It helps me to get clear about Configuration management and Change Request.
因此，我想确认我们的项目。
My project is to build the Window with blue color. But in executing, The window was painted with blue color. After that the stakeholder changed the color to yellow.
So, this should be managed by Change management or Configuration Management.
因为它会影响时间表，成本和产品规范。
Please explain.
Thank You so much.
This is the change in the specification, so configuration management.
Hello Fahad,
Please Read this sections from the PMBOK® Guide Sixth Edition, and then correct your answer and please also try to understand it well. What you are saying about configuration management and change management isn’t True at all.
“Configuration management plan:
Describes how the information about the items of the project (and which items) will be recorded and updated so that the product, service, or result of the project remains consistent and/or operative.
“变更控制should be applied once the first version of a deliverable has been completed. The control of the multiple versions or editions of a deliverable (e.g., documents, software, and building blocks) is supported by configuration management tools and procedures.”
“在建立基准之前，不需要更改由性能集成更改控制过程正式控制。一旦项目底线，更改请求就会完成此过程。一般而言，每个项目的配置管理计划应定义需要将哪些项目工件放在配置控制下。配置元素中的任何更改均应正式控制，并需要更改请求。”
“Configuration management activities such as: how changes will be initiated; how impacts will be analyzed; how they will be traced, tracked, and reported; as well as the authorization levels required to approve these changes;”
谢谢.
您好Shady，尽管可以将更多的技术细节添加到此博客文章中，但此处讨论的观点是有效的。
Mean is 20.0
Apply rule of 7,the output data are out of control and need investigation.
嗨法赫德,上面我也有同样的问题,为什么change management is a subset of configuration management instead another way around. Is there any reasoning behind?
Also have another question which made me confuse,
Ques: project manager doing quality check for steel bolts of 20 cm. The acceptable control limits are 19.955 cm and 20.045 cm. The measurements made at the end of the process yielded the following results : 20.033 cm, 19.982 cm, 19,995 cm, 20.006 cm, 19.970 cm, 19.968 cm, 19.963 cm, 19.958 cm, 19.962 cm, 19.979 cm and 19.959 cm. What should be done?
我总是认为，如果控制限制很好，为什么我们需要研究这一过程？它是否通常不像公差那样控制限制（除了PR由PM定义，以后由客户定义。）
Thanks
Sumit
与变更管理相比，配置管理具有更大的范围。
控制限制是由项目管理器设置的，以控制该过程，如果有任何内容，他将检查尽管项目在可接受的范围内，但一切都正确。
在我看来，配置的变化也可能影响成本，计划基线；或可能会引起一些风险。在这种情况下，需要根据影响来启动管理。因此，更改管理可以是配置的子集。
Please share your thoughts about my views .
Change management is a subset of configuration management.
您能解释一下为什么变更管理系统是配置管理系统的子集吗？
While opposite can be true but how change management system falls under configuration management system.
This is as per the definition which was defined by the PMI.
Dear Fahad,
Can you please provide a reference to this from PMI..?
如果您可以访问PMBOK指南第五版，则可以参考第53bob手机客户端2页。
感谢Fahad的解释，但是根据您的解释，一个问题主要用于产品和更改主要集中在基线和项目计划上，因此我看到，在许多方面，它们都会聚在一起，例如对于您的情况2现在需要将教室数量从10个更改为20个，现在可以更改产品，但是要满足该产品，您也需要更改计划，因此，在这种情况下，我们将通过配置和更改，如果我错了
Thanks again
In short, change management is a subset of configuration management.
哇，这很有趣和声音
谢谢。
You are welcome Lungile.
Any changes in the project management plans and all its subsidiary plans and baselines requires to be updated through change control process and have it approved. Then do all project documents would need to go through the change control process before updates can be made? e.g. stake holder register or risk register or requirement documents. Can these by updated without going through a formal change control process and approval? Can the PM make the changes without some else’s approval?
These are the project document and supposed to be updated all the time throughout the project lifecycle. They do not require to go through this process.
那么所有项目文件是否都以相同的方式处理？PMBOK指南第78页中还有一系列文档清单。除了绩效数据和问题/更改日志bob手机客户端/预测等明显的文档外，所有其他文档都可以在未经正式更改控制批准的情况下进行更新吗？
As per my understanding – yes.
Thanks so much Fahad for this piece, it brings simplicity and gives clarity to differentiate between Configuration and Change Management System.
欢迎您Kemisola。
Dear
谢谢very murch for the nice explanition.
Really I like it specially that I am starting the course of PMP preparation for the PMP exam.
谢谢，富丽堂皇。
Abdulmohsen
Thanks Abdulmohsen for your visit and leaving comment.
thanks, very clear now
You are welcome Aleciri.
I don’t agree this clarification, PMBOK does not very clearly distinct the two, my impression is that configuration management is super set of change manamement, plus some document record repository functions.
Okay.
can we say that change in spécifications (configurations) can be similar to change to product quality attributes? what is the difference between both of them? please i need clarification
thanks in advance !
What do you mean by product quality attribute?
I think Configuration Management is basically how will you manage the ‘integrity’ of your products/artifacts, how will all the stakeholders know what’s the latest blueprint to reference, what’s the latest architecture diagram, what’s the latest design document, what’s the latest source code to act one, etc.
The Change Management is just any changes, even the ones which doesn’t result in any change to Scope, Cost, Schedule.
Please read the blog post again.
Good explanation. Fahad, thank you and also others who have contributed.
You are welcome Jaleel.
Thanks a lot. and also to those who contribute in comments.
Your explanations clear my understandings.
谢谢all.
You are welcome Maythawda.
你好，
更改管理=项目更改。
配置管理=产品更改。
ri8？
Right.
Configuration management system is the system defining what your final product look like in specific and technical details.
Change control system: the set of procedures and processes that you need to apply in order to make a change
伟大的作品法哈德。这对我有帮助
谢谢约瑟夫。
I find a similar article on linkedin, and it is matching word by word. You can have a look at it:
https://www.linkedin.com/pulse/configuration-management-system-vs-change-bsc-pmp-pmi-rmp-tot-
The guy has copied my content and posted there. I have filed a copyright infringement notice with LinkedIn.
感谢阿米特让我知道。
Dear Fahad, Thanks for your great explanation, But I’m still little confused about the configuration management system.
Let’s take your instance ( Increasing the number of classrooms from 10 to 15), That’s great.
You said that any chang to the project processes or baseline is considered as a change management system, So in the previous instance ,when we decide to increase from 10 to 15 , I think this change affects directly the scope of the project, which is in turn one of the project baseline.
因此，我认为这将在变更管理系统之下。
Waiting for more information,and thanks in advance.
Change management is a subset of configuration management.
The change management plant defines the process for managing changes on the project.
The PMBOK Guide fifth edition, page: 138
这篇文章是如此有用。因此，更改管理计划是配置管理计划权利的子集。但是，如果问一个问题 - 更改管理计划包含什么？正确的答案是项目管理计划或配置管理计划。为什么？
谢谢in advance
很好地解释了最令人困惑的差异之一。
Thanks AG for stopping by and leaving your comment.
您的网站很棒！说明/澄清很棒！下载了您的指南，希望它们有用！
感谢尖叫的评论。
Who will initiate or approve the change request. When we will raise change request and when we can update project without change request.
To understand the whole process I suggest you read the Integration Management Knowledge area from the PMBOK Guide.
巴西，
更改控件转到CCB变更控制委员会以批准或拒绝请求。在某些项目中，赞助商赋予了项目经理批准一些变更请求的某些权力，这取决于合同，角色和职责。
Change management is a subset of configuration management.
不错的帖子法哈德！
In your one of the example in the blog. When client requested to increase the room numbers from 10 to 15. The Configuration Change is evident…Agreed!. But doesn’t a Change Request comes into picture, since adding more rooms would cause change in Project baseline i.e. Cost,schedule. E.g, work packages produced by taking 10 rooms into account… Kind of confused here. Please advise.
非常感谢您如此易于理解和简单的解释。
You are welcome Anusha.
欢迎您拉姆。
Hi Fahad,
这是一个很好的解释Vs进行改变guration Management. Thanks for such wonderful comparison & vivid clarification.
To Summarize from the above,
1.更改管理是配置管理的子集
2. Change Management is applicable for Process/Baseline changes.
3. Configuration Management is applicable for Product changes & updated document repository.
4. Both undergoes integrated change control process.
Regards,
Ram Narayan
Thanks Fahad, I have passes PMP Exam last week with 4P & 1MP, in first attempt.
感谢您的博客向我和所有PMP有抱负的人提供的所有支持。
恭喜ASIF通过PMP考试，我很高兴我能为您提供一些帮助。
Dear Fahad:
Your explanations are awesome for PMP aspirants, reference to this discussion, can you clarify in which PMI process Change management Plan &/if , Configuration Management Plan is developed , According to PMBOK -5????
谢谢，祝您好心...
In develop project management plan.
The PMBOK Guide page: 77
谢谢
You are welcome Aretit.
Brilliant explanation! Keep up the good work, Sir.
Thank You!
Thanks Janak.
Did PMI answered your question?
Thanks
No, I did not receive the reply from the PMI.
I just luv the way you make things simpler.
Amazing job.
谢谢, kindly
Thanks Sarika for your comment.
感谢您的博客信息。它对我有帮助。谢谢。
Abhijeet感谢你的评论。
晶体清楚地解释了这个主题。非常感谢！！！！
不客气迈克尔。
Are Configuration Management and Change Management differing from Configuration control and change control?
In the PMBOX Guide fifth ed. Says: Configuration control is focused on the specification of both the deliverables and the process while you mentioned In the Configuration Management System, changes related to product specification are managed.
谢谢.
Please refer page 532, the PMBOK Guide 5th edition.
Dear Fahad,
您的工作令人印象深刻。但是您能澄清萨德的疑问吗？我也分享。
Documenting changes in scope/configuration of the product (deliverable) is configuration management
Documenting change in processes/cost baseline/schedule baseline is change management.
Is this understanding correct? If yes, pg. 96 of PMBOK 5th ed. says “Configuration control is focused on the specification of both the deliverables and the process “. How come configuration control is focused on specification of the process? This is description of change control right?
我觉得这两个地方提到的配置管理的定义之间存在一些差异。
Anyway, I’m going to write a mail to PMI, let’s us see their reply.
是的，我们应该。请更新我们。
To my understanding, the configuration management affects both, the product and process where as change management only affects the process.
当管理对产品规范的更改（配置）时，它可以“可以”将更改与时间表和/或成本合并。两者都必须经过相同的集成变更控制，仅影响产品规范或项目过程或两者兼而有之。尽管在PMBOK中并不特别提及，但我认为，尽管变更管理可以单独采取行动，但配置管理必须沿着变更管理进行，但可能是子集或随附的文档。
Please correct me, if I am missing/ deviating.
I have written to PMI. I hope they will reply within this week.
Tauseef, I agree with your assessment: “Change management may act alone, [but] the configuration management has to take change management along”.
同样，基于PMBOK 5.6.1.1 - 控制范围描述了配置管理计划，该计划本身似乎定义了 *可构型 *的特殊性（因此，在哪种情况下，配置控件适用）。
我之所以发生在这个博客上，是因为我的PMP认证考试预备研究问题之一断言配置管理“不代替变更管理系统，而是与之合作”。
你好，
请您告诉我什么之间有什么不同：
Change management plan & change management system
Also configuration management plan & configuration management system
非常感谢
Imad
Basically you are asking the difference between plan and system.
Plan is something documented which guides you in your act. System is something that helps you implementing your plan.
希望能帮助到你。
我们可以说：配置管理将包括更改管理，但更改管理将不包括配置管理。
In other words: If we back to the building school example:
1- When client change form 10 to 15 classes: We should do configuration management and change management.
2-当项目时间表延迟一周时：我们应该更改管理。
Configuration management and change management are different to each other.据我了解，在配置MGMT中，我们根据Change MGMT批准的变更顺序或变化顺序进行了相应的自定义。
You can say that the change management is a subset of the configuration management.
Thanks for grate emample
谢谢Vara for your comment!
Hi Fahad,
Does both configuration & change management have to be done through the integrated change control process and also will this directly affect the project management plan ?
Yes, they have to be done through the integrated change control process. It may or may not affect the project management plan.
Thnks Fahad。
Hi Fahad
I read your post about change management and configuration management . I still have some concerned about all this term.
配置管理和变更管理系统
变更管理计划和变更控制系统
Can someone gives me more explanation and difference between these four terms with example it would be nice
Thanks in advance for you contribution to my understanding
best regard
来到PMP Sathish的世界和上帝的运气
Hi Fahad,
我通过了考试。感谢您的博客信息。它对我有帮助。谢谢。
Congratulation Sathish!
Useful one and clarified my doubts with your example.
Regards
Pullikol
You’re welcome Pullikol…
非常感谢Fahad
Hi Shariff,
Excellent explanation with good example. Thanks. Can you also explain different between change management system and configuration management system.
Hi Thathish,
我的理解,配置和变化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.
嗨，沙里夫，
configuration management system is from pmis but i think and i could be wrong change control is from opa. another question is change management the same as change control. thanks.
Fahad,
您对变更和配置管理之间差异的解释是有效的。我想补充一点，配置管理还包括管理文档的更改（使项目团队知道哪个版本是当前的）以及在此工作中采用的组织工具。
Regards,
Shariff
惊人的。非常感谢您的惊人解释
不客气。
Dear Fahad,
Keep on explaining the things like your way!!
感谢您的评论Ritesh。
Excellent Clarifications…. Difficult to forget now…Thanks…
不客气。
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 ?
它在那里谈论了这些文档的最新版本……当有批准的更改请求时，我们对基线进行了更改。
你好shweta，
Did Sangeetha give you the answer? If not, then could you be little more specific?
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.
变更管理包括时间表和成本基准的变化。
我不这么认为，因为更改范围会增加新的范围和新的相关Spécification。但是，通过将Spécifications更改为现有范围来涉及配置。因此，我认为更改范围与变更管理系统有关，而不是配置管理系统
Yes, you are right, if there is change in product scope then we can say it will be managed through the configuration change management system.
正如Nedhir所说，如果发生范围更改，则应将其视为变更管理。像学校的示例一样，如果教室的颜色从绿色变为黄色，则应该更改配置
hi Fahad,
thanks for spreading the knowledge. why configuration management system belongs to EEF and the change control belongs to OPA and they are both related. thanks.
hi fahad,
i found this video which explain the difference between the two:
更换管理层vs. Configuration Management – PMP Exam Prep
https://www.youtube.com/watch?v=VErsnGIqzEQ
Thanks for sharing Michael.
good
谢谢Aretit。