项目环境是动态的，并且在过程，计划或范围等领域的变化是恒定的。您可以将这些更改分为两类：
- 更换管理层
- 配置管理
“变更管理”是第一类。在这里，您可以管理与项目管理计划，流程和基线有关的更改。
在第二类中，您管理与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.
变更管理是项目管理中的著名术语，但配置管理不是。在IT领域中，经常使用“配置管理”一词，因此，如果您不在这个行业中，则可能会面临理解该概念的问题。
作为非专业人士，我进行了这场斗争。但是，既然我已经通过了PMP和PMI-RMP考试，我可以帮助您了解此博客文章中的概念。
请注意，变更管理和配置管理是最重要的概念PMP exam，您将看到有关它们的许多问题。
变更管理系统
根据PMBOK指南，“变更控制的重bob手机客户端点是识别，记录和控制更改the projectand the项目基线。”
在变更管理系统中，您可以管理与项目范围，计划和基准相关的更改。
例如，您用光了资金，需要额外的资金来完成该项目，因此，您将提出更改请求，以供额外资金。或者，您可能无法在指定的时间内完成项目，并且需要时间延长。
In the change management system, the change request is analyzed for any possible impact on any other项目目标. 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 concernedstakeholders.
更换管理层Activities
您在变更管理期间进行以下操作：
- Identify the changes.
- 为更改准备适当的文档。
- Review, analyze, and make a decision for the change request.
- 确保请求已实施，注册和传达。
配置管理System
根据PMBOK指南，“配置控制着重bob手机客户端于可交付成果和流程的规格。”
在配置管理系统中，您可以管理与产品规范和过程相关的更改。
例如，假设您正在开发产品，并且客户要求增加一些额外功能。
由于此更改与产品的配置有关，因此您将使用配置管理系统处理此更改。
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
您在配置管理期间进行以下操作：
- 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.
This will delay the project. 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.
这是在客户端更改产品配置时更改产品范围的请求。
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 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
以下是变更管理的一些条件：
- 延迟时间表：您将必须制定一个新的时间表来反映当前情况。
- 成本overrun:You will need to re-estimate your cost to complete the project.
配置管理条件
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
变更管理和配置管理不会争夺相同的空间。它们用于不同的目的。
根据PMBOK指南，“配置控制着重bob手机客户端于可交付成果和流程的规范，而更改控制的重点是识别，记录和批准或拒绝对此的更改项目文件, deliverables, or baselines.”
产品配置的任何更改也会影响项目范围，您将更新项目计划，成本和计划基准。
Configuration management has a larger scope than change management.
谁可以提出更改和配置请求，谁可以授权？
任何人都可以提出更改请求，但必须由项目经理或更高的权威批准，如配置或变更管理计划中所述。如果客户不参与该过程，则需要他们的同意才能实施更改请求。
更高的权力可以是项目管理计划中提到的变更控制委员会（CCB），项目管理办公室（PMO）或任何其他利益相关者。
关于配置请求通常，它来自客户端，因为它涉及产品的更改。
该请求由项目经理审查，然后转发给有关的高级权力，以供其审查和批准。可能需要客户的协议，因为他们必须支付任何其他功能。
概括
变更管理和配置管理是集成管理的一部分，并且都涉及项目或产品中可能发生的所有更改。变更管理与与计划，过程和基准相关的更改有关，而配置管理涉及与产品范围相关的更改。项目经理的工作是提出这些请求，并确保对它们进行适当的审查。一旦做出决定，应立即实施。
Now I hope you will not have any problems in solving questions on the PMP exam regarding change management and configuration management systems.
您如何管理项目的更改？请通过评论部分分享您的经验。
你好法哈德，
Thank you for your well thought out article.
我喜欢您的定义，看起来正确；当然，解释PMBOK的一种方法。但是，问题的一部分（以及为什么您写了这篇文章以及像我这样的人以及其他读者寻求澄清的人），PMBOK非常使它成为一笔模糊的交易。您的定义很好，很有意义，这也是我所拥护的：配置与产品有关；变化与项目文档，基准，流程等有关，但是存在矛盾。
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.
所有这么说：PMBOK由许多人撰写，然后在其各种作者和章节上“控制”以确保整体完整性。但是仍然存在不陈述和矛盾 - 我相信这是一个。他们似乎用新版本的PMBOK清除了这些，但其他版本出现了。所有这些都说，您的定义是一个很好的定义 - 我一直认为是真实的。现在我开始怀疑。阅读并现在研究PMBOK，因此试图理解“ PMBOK如何定义此问题”，因为如前所述，PMBOK的定义并不总是同一个人的“现实世界”定义。没关系，他们还不清楚，他们的方法中存在矛盾。谢谢。很棒的文章。如果您可以或可以与他们对话 - 告诉PMI澄清他们的定义！ 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,
更改管理是配置管理的子集。
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
在项目中间，我的钢铁工作承包商脱离了工作，我必须找到一个替代品。我找到了另一种选择，但是新承包商将在一个星期内开始从事该项目。
This will delay the project. Therefore, I will raise a change request for a one-week extension of the schedule through the change management system.
示例2
现在，我正在建造一座学校建筑物，客户要求我必须将房间数量从10到15增加。
这是在客户端更改产品配置时更改产品范围的请求。
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 !
在这两种情况下，您都会提出更改请求。
Dear Fahad,
您能否提供PMI的参考。
如果您可以访问PMBOK指南第五版，则可以参考第53bob手机客户端2页。
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.
太感谢了。
This is the change in the specification, so configuration management.
你好法哈德，
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.
“一旦可交付的第一个版本完成，应应用变更控制。配置管理工具和过程支持了可交付的多个版本或版本（例如文档，软件和构建块）的控制。”
“Before the baselines are established, changes are not required to be formally controlled by the Perform Integrated Change Control process. Once the project is baselined, change requests go through this process. As a general rule, each project’s configuration management plan should define which project artifacts need to be placed under configuration control. Any change in a configuration element should be formally controlled and will require a change request.”
“配置管理活动，例如：如何启动更改；如何分析影响；它们将如何追踪，跟踪和报告；以及批准这些更改所需的授权水平；”
Thank you.
您好Shady，尽管可以将更多的技术细节添加到此博客文章中，但此处讨论的观点是有效的。
Hi Fahad, i also have same question above that why 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定义，以后由客户定义。）
谢谢
Sumit
与变更管理相比，配置管理具有更大的范围。
控制限制是由项目管理器设置的，以控制该过程，如果有任何内容，他将检查尽管项目在可接受的范围内，但一切都正确。
谢谢Fahad for your explanation,but one question, according to your explanation, configuration is mainly for product and change is mainly focus on baseline and project plans, so i see that at many points they will be meet together, like for scenario 2 when u need to change the number of classrooms from 10 to 20 now yes that change in the product, but to meet that product you will need to change the plans as well, so in that scenario we will pass by both configuration and change, correct me if im wrong
谢谢again
In short, change management is a subset of configuration management.
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手机客户端/预测等明显的文档外，所有其他文档都可以在未经正式更改控制批准的情况下进行更新吗？
根据我的理解 - 是的。
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.
感谢阿米特让我知道。
亲爱的法哈德，感谢您的出色解释，但我仍然对配置管理系统感到困惑。
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.
更改管理是配置管理的子集。
The change management plant defines the process for managing changes on the project.
PMBObob手机客户端K指南第五版，第138页
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.
Thank you.
Please refer page 532, the PMBOK Guide 5th edition.
Dear Fahad,
您的工作令人印象深刻。但是您能澄清萨德的疑问吗？我也分享。
Documenting changes in scope/configuration of the product (deliverable) is configuration management
记录流程/成本基准/时间表基准的变化是变更管理。
这是正确的理解吗?如果是,pg。96 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.
是的，我们应该。请更新我们。
Tauseef，我同意您的评估：“变更管理可以单独采取行动，但配置管理必须沿着变更管理进行。”
同样，基于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.
希望能帮助到你。
Hi Fahad
我阅读了您有关变更管理和配置管理的帖子。我仍然对所有这个术语感到担忧。
配置管理和变更管理系统
变更管理计划和变更控制系统
Can someone gives me more explanation and difference between these four terms with example it would be nice
谢谢in advance for you contribution to my understanding
best regard
Hi Fahad,
Can we say Configuration management is scope change and change management is shcedule change?
谢谢
拉梅什
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所说，如果发生范围更改，则应将其视为变更管理。像学校的示例一样，如果教室的颜色从绿色变为黄色，则应该更改配置