项目环境是动态的,并且在过程,计划或范围等领域的变化是恒定的。您可以将这些更改分为两类:
- Change Management
- Configuration Management
“变更管理”是第一类。在这里,您可以管理与项目管理计划,流程和基线有关的更改。
In the second category, you manage changes related toproduct scope,称为配置管理。
建立基准时需要更改请求,您必须对其进行更改。如果未设置基线,则无需正式更改请求。更改请求和配置请求是集成管理系统的一部分。
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.
作为非专业人士,我进行了这场斗争。但是,既然我已经通过了PMP和PMI-RMP考试,我可以帮助您了解此博客文章中的概念。
Please note that change management and configuration management are the most important concepts for thePMP exam, and you are going to see many questions on them.
Change Management System
According to the PMBOK Guide 6th edition, “Change Control is focused on identifying, documenting and controlling changes tothe project和项目基线。”
In the change management system, you manage the changes related to the project scope, planning, and baselines.
For example, you run out of money and you need additional funding to complete the project, therefore, you will raise a change request for additional funds. Or, you may not be able to complete your project within the specified time and require a time extension.
在变更管理系统中,分析了对任何其他项目目标的任何可能影响的变更请求。之后,请求要么被批准或拒绝。
To minimize disruption, a change management system must ensure that all parameters are identified and analyzed for any possible impact.
如果批准了变更请求,您将更新相关的基准,更新项目文件并通知相关利益相关者。
Change Management Activities
您在变更管理期间进行以下操作:
- Identify the changes.
- Prepare proper documentation for the changes.
- 审查,分析并决定更改请求。
- 确保请求已实施,注册和传达。
Configuration Management System
According to the PMBOK Guide 6th edition, “Configuration Control focuses on the specifications of both the deliverables and the processes.”
在配置管理系统中,您可以管理与产品规范和过程相关的更改。
例如,假设您正在开发产品,并且客户要求增加一些额外功能。
由于此更改与产品的配置有关,因此您将使用配置管理系统处理此更改。
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.
Configuration Management Activities
You do the following during configuration management:
- Identify the configurable items.
- Record and prepare a report for all configurable items.
- Verify and conduct an audit of all configurations are as per the requirements.
A Real World Example of Change and Configuration Management
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
您正在建造一座学校建筑物,客户要求您将房间数量从10到15增加。
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.
请注意,在第一种情况下,你提高了change request to increase the deadline of the project by one week. There was no change to the product, the change was only needed in the schedule baseline; the school building was the same, but you will hand over this building to the client one week later.
变更管理和配置管理系统之间的区别
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:
- 延迟时间表:您将必须制定一个新的时间表来反映当前情况。
- Cost 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.
更改管理与配置管理
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.
Who Can Raise a Change and Configuration Request and Who Can Authorize It?
Anyone can raise a change request but it must be approved by the project manager or a higher authority, as mentioned in the configuration or change management plan. If the client is not involved in the process, their consent is required to implement the change request.
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.
Regarding a configuration request, usually, it comes from the client as it involves a change in the product.
This request is reviewed by the project manager and then forwarded to the concerned higher authority for their review and approval. An agreement from the client may be required because they have to pay for any additional features.
概括
变更管理和配置管理是集成管理的一部分,并且都涉及项目或产品中可能发生的所有更改。变更管理与与计划,过程和基准相关的更改有关,而配置管理涉及与产品范围相关的更改。项目经理的工作是提出这些请求,并确保对它们进行适当的审查。一旦做出决定,应立即实施。
Now I hope you will not have any problem in solving questions on the PMP exam regarding change management and configuration management systems.
您如何管理项目的更改?请通过评论部分分享您的经验。
你好法哈德,
Thank you 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.
Change Management” is the first category. Here you manage changes related to project management plans, {processes}, and baselines.
According to the PMBOK Guide 6th edition, “Configuration Control focuses on the specifications of both the deliverables and the {processes}.”
I don’t understand how the 2 terms dealing with{ process }
kindly clarify it.
Hello Anas,
更改管理是配置管理的子集。
Hi Mr. Fahad,
Now, if the client request change in my scope,
I need to go with Change management and configuration management in parallel
Hello Anas,
I believe he is asking for change in product scope. In this case, you will go for configuration management.
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
During the middle of the project, my contractor for steel work walks off the job and I have to find a replacement. I found an alternative, but the new contractor will not start working on the project for a week.
这个项目将推迟。因此,我将意大利广播电视公司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.
那是一个很棒的兄弟。非常感谢您在这种情况下更好地理解这些概念。
You are welcome Muhammed.
Partly wrong explanation…
你好tunc,什么部分是什么部分?
Fantastic !
谢谢巴巴克。
Great explanation, you clearly point out the confusing I have on this part. Thank you so much.
You are welcome Kenny.
很有用
谢谢Shriram的评论。
谢谢。
更改管理处理项目范围,而配置管理处理产品范围。
Correct.
400个问题在模拟中?
你好马哈富兹,
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,
谢谢for your comment.
Great writeup. The configuration management is new to me and your post was useful. Thanks.
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.
因此,这应通过变更管理或配置管理来管理。
Because it impacts to schedule, cost and product specification.
请解释。
Thank You so much.
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.
“配置管理计划:
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.
“Change control 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.”
“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,尽管可以将更多的技术细节添加到此博客文章中,但此处讨论的观点是有效的。
Mean is 20.0
Apply rule of 7,the output data are out of control and need investigation.
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?
还有另一个使我感到困惑的问题,
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?
I always think if control limits are good why we need to frther investigate the process? Is it not control limits are typically similar like tolerances (except prior is defined by PM and later by customer.)
谢谢
Sumit
Configuration management has larger scope as compared to change management.
Control limits are set by project manager to control the process and if anything goes outside of it, he will check if everything is right though the project is within acceptable range.
在我看来,配置的变化也可能影响成本,计划基线;或可能会引起一些风险。在这种情况下,需要根据影响来启动管理。因此,更改管理可以是配置的子集。
请分享您对我的观点的想法。
更改管理是配置管理的子集。
Can you explain why the change management system is a subset of the configuration management system?
虽然相反的可能是正确的,但是更改管理系统如何属于配置管理系统。
这是根据PMI定义的定义。
亲爱的法哈德,
Can you please provide a reference to this from PMI..?
If you have access to the PMBOK Guide 5th edition, you can refer to page 532.
法赫德感谢你的解释,但是一个问题, 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.
Wow it is very interesting and sound
thank you.
欢迎您的肺。
项目管理计划及其所有子公司计划和基准的任何更改都需要通过变更控制过程进行更新并获得批准。那么,所有项目文档是否都需要在更新之前进行更改控制过程?例如利益持有人登记册或风险登记册或要求文件。可以通过更新而无需进行正式的更改控制过程和批准来进行更新吗?PM可以在未经其他批准的情况下进行更改吗?
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.
谢谢so much Fahad for this piece, it brings simplicity and gives clarity to differentiate between Configuration and Change Management System.
You are welcome Kemisola.
Dear
Thank you very murch for the nice explanition.
Really I like it specially that I am starting the course of PMP preparation for the PMP exam.
谢谢and regalrds.
Abdulmohsen
感谢Abdulmohsen的访问并发表评论。
谢谢,现在很清楚
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.
好的。
我们可以说,Spécifications(配置)的变化与产品质量属性的变化可能相似吗?他们两个之间有什么区别?请我需要澄清
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.
更改管理只是任何更改,甚至没有导致范围,成本和时间表的任何更改的更改。
请再次阅读博客文章。
Good explanation. Fahad, thank you and also others who have contributed.
You are welcome Jaleel.
谢谢a lot. and also to those who contribute in comments.
Your explanations clear my understandings.
谢谢你们。
You are welcome Maythawda.
Hi,
更改管理=项目更改。
Configuration Management = Product Change .
Ri8?
Right.
Configuration management system is the system defining what your final product look like in specific and technical details.
更改控制系统:您需要应用的一组过程和过程以进行更改
伟大的作品法哈德。这对我有帮助
谢谢Joseph.
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-
这个家伙复制了我的内容并在那里发布了。我已经向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.
So, in my opinion, this will be under the change management system.
等待更多信息,并提前感谢。
更改管理是配置管理的子集。
The change management plant defines the process for managing changes on the project.
The PMBOK Guide fifth edition, page: 138
This post is so useful. So Change Management Plan is a subset of Configuration Management Plan right. However if a question is asked – Change Management Plan contains what? The right answer would be Project Management Plan or Configuration Management Plan. And why?
Thank you in advance
Very well explained one of the most confusing differences.
谢谢AG for stopping by and leaving your comment.
您的网站很棒!说明/澄清很棒!下载了您的指南,希望它们有用!
谢谢吱for your comments.
Who will initiate or approve the change request. When we will raise change request and when we can update project without change request.
理解整个过程我建议你阅读the Integration Management Knowledge area from the PMBOK Guide.
巴西,
CHANGE CONTROLS GO TO CCB CHANGE CONTROL BOARD TO APPROVE OR REJECT THE REQUESTS. IN SOME PROJECTS, THE SPONSOR GIVES SOME AUTHORITY TO THE PROJECT MANAGER TO APPROVE SOME CHANGE REQUESTS AND IT DEPENDS ON THE CONTRACT AND ROLES AND RESPONSIBILITIES.
更改管理是配置管理的子集。
不错的帖子法哈德!
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,
这是对变更与配置管理的绝佳解释。感谢您的精彩比较和生动的澄清。
To Summarize from the above,
1. Change Management is the Subset of Configuration Management
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.
问候,
内存Narayan
谢谢法哈德,我上周以4P和1MP的优势通过了PMP考试。
谢谢for all the support your blog have provided to me & all PMP aspirants.
Congratulations Asif for passing the PMP exam and I am glad that I could be of some help to you.
亲爱的法哈德:
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????
谢谢& best wishes…
In develop project management plan.
The PMBOK Guide page: 77
Thank you
You are welcome Aretit.
Brilliant explanation! Keep up the good work, Sir.
Thank You!
谢谢Janak.
Did PMI answered your question?
谢谢
No, I did not receive the reply from the PMI.
I just luv the way you make things simpler.
很棒的工作。
非常感谢你
感谢Sarika的评论。
感谢您的博客信息。它对我有帮助。谢谢。
谢谢Abhijeet for your comment.
晶体清楚地解释了这个主题。非常感谢!!!!
You are welcome Michael.
配置管理和更改管理是否与配置控制和更改控制不同?
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.
亲爱的法哈德,
您的工作令人印象深刻。但是您能澄清萨德的疑问吗?我也分享。
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?
I feel there is some discrepancy between the definition of configuration management mentioned in these two places.
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.
When a change to a product specification is managed (configuration), it “may” incorporate change to schedule and/ or cost as well. Both have to go through same Integrated Change Control, affecting either only to the product specification OR project process OR both. Though not particularly mentioned in PMBOK, I assume, while change management may act alone, the configuration management has to take change management along, may be as a subset or as an accompanying document.
Please correct me, if I am missing/ deviating.
I have written to PMI. I hope they will reply within this week.
Tauseef,我同意您的评估:“变更管理可以单独采取行动,但配置管理必须沿着变更管理进行。”
同样,基于PMBOK 5.6.1.1 - 控制范围描述了配置管理计划,该计划本身似乎定义了 *可构型 *的特殊性(因此,在哪种情况下,配置控件适用)。
I only happened across this blog because one of my PMP Certification Exam Prep study questions asserted that Configuration Management “does NOT take the place of a Change Management System, but rather works with it”.
Hi,
Please can you tell me what is different between :
Change management plan & change management system
Also configuration management plan & configuration management system
Thank you very much
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.
Hope it helps.
我们可以说:配置管理将包括更改管理,但更改管理将不包括配置管理。
In other words: If we back to the building school example:
1-客户更改表格10至15类时:我们应该进行配置管理和更改管理。
2-当项目时间表延迟一周时:我们应该更改管理。
Configuration management and change management are different to each other.From what I understand, in configuration mgmt we customize accordingly to the change order or variation order that have been approved by change mgmt.
You can say that the change management is a subset of the configuration management.
谢谢for grate emample
Thank you 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 ?
是的,它们必须通过集成的变更控制过程来完成。它可能会或可能不会影响项目管理计划。
Thnks Fahad.
Hi Fahad
I read your post about change management and configuration management . I still have some concerned about all this term.
配置管理和变更管理系统
Change management plan and change control system
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
来到PMP Sathish的世界和上帝的运气
Hi Fahad,
我通过了考试。感谢您的博客信息。它对我有帮助。谢谢。
Congratulation Sathish!
有用的一个,并以您的榜样澄清了我的疑问。
Regards
Pullikol
You’re welcome Pullikol…
thank you very much Fahad
Hi Shariff,
Excellent explanation with good example. Thanks. Can you also explain different between change management system and configuration management system.
嗨,那是
据我了解,配置和变更管理系统都是组织项目管理信息系统的组成部分。但是,配置管理系统由识别,记录和控制产品,服务和结果功能和物理特征的更改(包括跟踪系统和批准级别)中采用的记录程序组成。另一方面,变更管理系统定义了如何控制,更改和批准的项目可交付成果和文档。后者通常是前者的子集。请参阅Pbob手机客户端MBOK指南第428-429页。
I hope this clarification helps.
hi shariff,
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,
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.
问候,
Shariff
Awesome. Thanks a lot for your amazing explanation
You are welcome.
亲爱的法哈德,
Keep on explaining the things like your way!!
谢谢for your comments Ritesh.
Excellent Clarifications…. Difficult to forget now…Thanks…
不客气。
但是在某些问题中,问您要去哪里找到文档,答案是配置管理。似乎也被认为是文档管理存储库工具,对吗?
There it talks about the latest version of the documents … Becoz we have changes to the baseline when there is an approved change request.
你好shweta,
Sangeetha给您答案了吗?如果没有,那么您会更具体吗?
Hi Fahad,
Can we say Configuration management is scope change and change management is shcedule change?
谢谢
内存esh
Configuration management is scope change – Yes, we can say this.
And Change Management includes the change in schedule and cost baselines.
我不这么认为,因为更改范围会增加新的范围和新的相关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.
As Nedhir said, if there is scope change, it should be considered as change management. Like the school example, if the color of the classroom is changed from green to yellow, then this should configuration change
hi Fahad,
感谢您传播知识。为什么配置管理系统属于EEF,而更改控件属于OPA,它们都相关。谢谢。
hi fahad,
i found this video which explain the difference between the two:
更改管理与配置管理 - PMP考试准备
https://www.youtube.com/watch?v=VErsnGIqzEQ
谢谢for sharing Michael.
good
谢谢Aretit.