TOPIC: Change Requests and Approved Change Requests flow

While we see most of the process create change requests, except the following 3 processes contain the Approved Change Requests as an input and also Change Requests as an output, what are the kind of scenarios that may lead to create change requests and get them approved?
Direct and Manage Project Work,
Control Quality,
Control Procurements.

Hello Ashwin, this is a great observation. There are several processes that could trigger change requests without the need to observe Approved Change Requests. For instance, the Execution Process Group commands the greatest amount of project work, effort, and resources. Likewise, the resulting planning and rebaselining from this process group necessitates changes i.e. reconsolidating resources, changes to resource productivity, schedule changes, budget changes, and changes to unforeseen risks.

These fluctuations will normally alter the overall project management plan in some way, whether the impact is favorable or negative. A project manager and the project team should analyze the deviations impacting schedule, resource, scope, etc. The analysis will ultimately provoke change requests that must be assessed and evaluated. When change requests are approved the project management plan and various baselines need to be adjusted as a result.

Approved Change Requests still need to be analyzed and evaluated as the project is executed; this is why processes like Control Quality require the implementation of analytical tools, such as the seven basic quality tools, statistical sampling, and inspection. Perform Integrated Change Control must follow once new change requests are created as an output of Control Quality.

Did I explain that well enough? I wanted to make these examples as general as possible so everyone could relate and understand them. Please let me know if you have anymore questions on this topic and I'd be more than happy to help.

Thanks Robert. Coming to the Manage Communications area where we update the OPA that contains the Stakeholder Notifications which has the Approved Changes, or the Project Reports / Document updates that contain the Issues Log, do the Change Requests reflect in some way here even though they may not be the direct input or Output?
How does Change Requests relate to the Manage Communications?
Also what is a general difference between an Issue Log and the Change Request? Any pointers here?

No problem at all, Ashwin. You are definitely on the right track. Approved change requests and updates could reflect as an input of OPA during the process of Managing Communications. Changes in OPA can be alterations with policies, processes, and procedures regarding communication's management; however, it's important to understand that these inputs are not known as Approved Change Requests. Change Requests are formalized changes that require formal approval, which could lead to changes in processes and procedures. However, the output of OPA updates is primarily what combines to make OPA once updated.

An Issue Log is merely a document to record and monitor the outcomes and resolutions to issues. This list of issues and resolutions can help others on the project understand who is responsible for fixing problems. This can also help communicate target dates and obstacles that could prohibit the team from achieving their goals.

A Change Request occurs when the team identifies an action or adjustment that is needed. This results in the output of a Change Request, such as revised schedule dates, resource requirements, cost estimates, quality standards, risk responses, etc. Alterations of the Project Management Plan and supporting documents can also be addressed through a change request. This is a formal written request that can be processed through the Perform Integrated Change Control process.

Does this help?