![]() During Execution, further Changes and/or new Change Requests are likely and hence it also will result in Change Requests, which will be again fed into “Perform Integrated Change Control” and follow Step – 5 and Step – 6.All “Approved Change Requests” have to be executed so that they are part of the Product/Service/Result and hence fed to “Direct and Manage Project Work” process in Integration Management in Executing process group.Changed Requests are approved by the “Change Control Board” (or Customer Control Board), operating under "Perform Integrated Change Control" process of Integration Management.All these “Change Requests” will be fed to “Perform Integrated Change Control” process to have “Approved Change Requests” as outputs. ![]() The exception is for "Perform Integrated Change Control" (PICC) process in Integration Management knowledge area. Most of the Executing processes will also have change requests as outputs. All Control/Monitor Processes (all of them, except 1), e.g., Control Scope, Control Schedule, Control Costs, Monitor Risks, will generate “Change Requests”.The exceptions are - Define Activities, Develop Schedule (first two in Schedule Management knowledge area), Plan Risk Responses (in Risk Management knowledge area), Plan Procurement Management (in Procurement Management knowledge area). Change Requests are typically not outputs of planning processes under Planning process group, except 4 processes.The exception is for "Identify Stakeholders" process in Stakeholder Management knowledge area. No Change Requests are created in any process/process area (out of 49) under “Initiating” (except 1), “or “Closing” process groups.Change Requests can be of these types – “Preventive Action”, “Corrective Action”, “Defect Repair”, and “Updates”.There are 11 key points to note in the flow of change requests.ġ1 Key Points to Understand Change Request Flow All of these are fed to PICC of Integration Management, from where the "Approved Change Requests" will be coming as output. CRs coming from other monitoring, controlling and executing, planning and initating processes from rest of the 8 knowledge areas are simply shown as inputs to "Perform Integrated Change Control" (PICC) process of "Integration Management" knowledge area.Īs shown above, various control process areas such as "Control Scope", "Validate Scope", "Control Schedule", "Control Costs", "Monitor Communications", "Control Procurements" - all will have Change Requests as their outputs. In the below diagram, the key processes from "Integration Management" knowledge area are shown along with one process from "Quality Management" knowledge area. If I take all the processes where CRs are inputs or outputs (part of ITTOs - Inputs, Tools an Techniques and Outputs), it will be quite complicated. But CRs are there in many of the 49 processes. PMBOK 6th edition doesn't explicitly inform on Change Requests (or simply CRs) flow across 10 Knowledge Areas and 5 Process Groups in a combined way. ![]() ![]() In the new edition of the PMBOK® Guide 6th edition, the flow of change request has changed. The earlier post of Change Request Flow, was one of the most read articles. In the real project world, you as a project manager, will definitely face change requests. In fact, certain life cycles thrive on changes. In project and project management too, changes will happen. It is said - change is the only constant in life. Change request is a key topic to know if you are preparing for the PMP exam.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |