Summarize this article. Provide yourthoughts.?????Configuration Management vs Change Management Done????Changes are inevitable in any project's orproduct's life cycle. Some changes haveeither positive or negative effects on theproject's baseline schedule, baseline budget,performance, and profitability. Otherchanges may affect the technicalspecifications and/or scope of a product.Although Configuration management andchange managementrefer to two differentconcepts, they are complementary to eachother. Many PMP aspirants are familiar withthe change management concept. However,configuration management is not well knownoutside the IT industry.As per The PMBOK Guide, ConfigurationManagement Plan and Change ManagementPlan are separate plans and they aresubsidiary plans of the Project ManagementPlan. In this article, we will discuss bothconcepts and their key aspects.What is ConfigurationManagement and Why is ItImportant?The configuration management focuses onhow any change to the "product" should bedone. Configuration management documentshow changes will be monitored andcontrolled. It is a process of definingconfigurable items (product, service, result,component) and controlling changes to suchitems. It can be considered as a versioncontrol system for the product.There are some conditions for configurationmanagement such as market conditions,client's requirements, and technologicaldevelopments.Competition in the market forces youto add new features to the product.Because your competitors develop theirproduct continuously.Due to technological developments,your product may become outdated.Therefore you must improve yourproduct and make inevitablemodifications to keep it updated.Client's requirements may change in time and your product may becomeweak to provide solutions. Thereforeyou must add new features consideringthe client's needs.DoneChange Management inProject ManagementThe change management focuses onhow any change to the "process"should be done. It is relevant to manykinds of changes to the project. Forthis process, a change managementplan should be prepared to managehow the changes will be handled,evaluated, documented, and managedthroughout the life cycle of theproject.There are some conditions for it suchas delay in schedule and costoverruns.OTime is one of the most importantcomponents of a project. If it isnot managed effectively, delaysand time overruns will occur. Ifthe delays are not recoverable,you must develop a new scheduleto deliver the project on time.• If the cost estimations areoutdated, you must develop a new project budget and re-estimate theproject costs.Configuration ManagementExampleSuppose you are managing a hospitalproject and the client requests you todo additional cabling for anautomation system that is not in yourscope. This request changes theproject designs, schedule, andbudget. Then you will raise theconfiguration change request and getit approved by the client. Thesechanges will be conducted under theconfiguration management systembecause the specification of theproduct is changed.Change ManagementExampleSuppose you are managing a pipelineproject and as per your contract landacquisition works are under theclient's responsibility. The Clientcouldn't complete land acquisitionworks on time and because of this,you delayed two months.Therefore, you will submit a changerequest to extend yourwork schedule hv twn months and will work schedule by two months and willtry to get it approved by the client.DoneAnother example is that you aremanaging a project to build a highway.One of your contractors walks off thejob. Activities under his responsibilitywere on the critical path. Although youassigned a new contractor for the job,you will not complete the project ontime.At this stage, you will raise a changerequest to extend the schedulebaseline by one month and will try toget it approved by the client.What is the DifferenceBetween ConfigurationManagement andChange Management?As we mention in the first paragraph,both concepts are complementary toeach other. However, there are somedifferences between them.OConfiguration managementfocuses on the configurable items(product, service, result, component) whereas changemanagement focuses on theprocess.OChanges to some of theconfigurable items may notrequire a formal changemanagement process.OChange management leads tomany kinds of changes that canimpact the baseline, whereasconfiguration management leadsto the changes which are specificto the product configuration.° A Change Management Planleads the project team in terms ofmaking any kind of change on theproject, especially the ones thatcan affect the scope, schedulebaseline, and cost baseline. Onthe other hand ConfigurationManagement Plan leads theproject team in making changesthat are related to the ProductConfiguration. Note: Somepeople think that configurationmanagement is only done for theproducts. This is not correct.Configuration management canbe done for any type of artifactincluding product, processes,plans, and baselines according tothe PMBOK Guide.

Question

Summarize this article. Provide yourthoughts.?????Configuration Management vs Change Management Done????Changes are inevitable in any project's orproduct's life cycle. Some changes haveeither positive or negative effects on theproject's baseline schedule, baseline budget,performance, and profitability. Otherchanges may affect the technicalspecifications and/or scope of a product.Although Configuration management andchange managementrefer to two differentconcepts, they are complementary to eachother. Many PMP aspirants are familiar withthe change management concept. However,configuration management is not well knownoutside the IT industry.As per The PMBOK Guide, ConfigurationManagement Plan and Change ManagementPlan are separate plans and they aresubsidiary plans of the Project ManagementPlan. In this article, we will discuss bothconcepts and their key aspects.What is ConfigurationManagement and Why is ItImportant?The configuration management focuses onhow any change to the &#34;product&#34; should bedone. Configuration management documentshow changes will be monitored andcontrolled. It is a process of definingconfigurable items (product, service, result,component) and controlling changes to suchitems. It can be considered as a versioncontrol system for the product.There are some conditions for configurationmanagement such as market conditions,client's requirements, and technologicaldevelopments.Competition in the market forces youto add new features to the product.Because your competitors develop theirproduct continuously.Due to technological developments,your product may become outdated.Therefore you must improve yourproduct and make inevitablemodifications to keep it updated.Client's requirements may change in time and your product may becomeweak to provide solutions. Thereforeyou must add new features consideringthe client's needs.DoneChange Management inProject ManagementThe change management focuses onhow any change to the &#34;process&#34;should be done. It is relevant to manykinds of changes to the project. Forthis process, a change managementplan should be prepared to managehow the changes will be handled,evaluated, documented, and managedthroughout the life cycle of theproject.There are some conditions for it suchas delay in schedule and costoverruns.OTime is one of the most importantcomponents of a project. If it isnot managed effectively, delaysand time overruns will occur. Ifthe delays are not recoverable,you must develop a new scheduleto deliver the project on time.• If the cost estimations areoutdated, you must develop a new project budget and re-estimate theproject costs.Configuration ManagementExampleSuppose you are managing a hospitalproject and the client requests you todo additional cabling for anautomation system that is not in yourscope. This request changes theproject designs, schedule, andbudget. Then you will raise theconfiguration change request and getit approved by the client. Thesechanges will be conducted under theconfiguration management systembecause the specification of theproduct is changed.Change ManagementExampleSuppose you are managing a pipelineproject and as per your contract landacquisition works are under theclient's responsibility. The Clientcouldn't complete land acquisitionworks on time and because of this,you delayed two months.Therefore, you will submit a changerequest to extend yourwork schedule hv twn months and will work schedule by two months and willtry to get it approved by the client.DoneAnother example is that you aremanaging a project to build a highway.One of your contractors walks off thejob. Activities under his responsibilitywere on the critical path. Although youassigned a new contractor for the job,you will not complete the project ontime.At this stage, you will raise a changerequest to extend the schedulebaseline by one month and will try toget it approved by the client.What is the DifferenceBetween ConfigurationManagement andChange Management?As we mention in the first paragraph,both concepts are complementary toeach other. However, there are somedifferences between them.OConfiguration managementfocuses on the configurable items(product, service, result, component) whereas changemanagement focuses on theprocess.OChanges to some of theconfigurable items may notrequire a formal changemanagement process.OChange management leads tomany kinds of changes that canimpact the baseline, whereasconfiguration management leadsto the changes which are specificto the product configuration.° A Change Management Planleads the project team in terms ofmaking any kind of change on theproject, especially the ones thatcan affect the scope, schedulebaseline, and cost baseline. Onthe other hand ConfigurationManagement Plan leads theproject team in making changesthat are related to the ProductConfiguration. Note: Somepeople think that configurationmanagement is only done for theproducts. This is not correct.Configuration management canbe done for any type of artifactincluding product, processes,plans, and baselines according tothe PMBOK Guide.

Accepted Answer

Configuration management and chain management are two distinct concepts, although they are mutually…