Neither PMI nor PMBOK says this.
It depends on your change management plan and structure, the importance of that resource, the impact of removing and etc.
...
1 reply by Manuel Perez
Sep 12, 2022 3:59 PM
Manuel Perez
...
In my past experience, a change order is needed whenever the scope, budget, or schedule in a commitment changes. Furthermore, unless a contract document specifies that a resource is a key resource as named in the required submittals, then you can remove/replace the resource without a change order.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
No, Abolfazi puts it right: it depends. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
Needing or not needing a COR is dependent on your governance structure, change management plan, level of authority granted to the PM and risk/impact of this change order so in general, I would say, it depends on the situation. It is not a one size fits all. Saving Changes...
Manuel PerezProject Management Coordinator| Las Vegas Valley Water DistrictNorth Las Vegas, Nv, United States
Sep 12, 2022 9:28 AM
Replying to Abolfazl Yousefi Darestani
...
Neither PMI nor PMBOK says this.
It depends on your change management plan and structure, the importance of that resource, the impact of removing and etc.
In my past experience, a change order is needed whenever the scope, budget, or schedule in a commitment changes. Furthermore, unless a contract document specifies that a resource is a key resource as named in the required submittals, then you can remove/replace the resource without a change order. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Manuel has it right. Not only should the contract tell you when you need a change order but it should also lay the foundation that cannot be altered without a contract amendment. (A contract amendment is NOT the same thing as a change order.) Saving Changes...
I disagree with the statement that the contract stipulates everything that requires a change order.
Change processes may affect lower level things such as business documentation invisible to the customer such as the WBS. Legal language typically tries to avoid saying what is *not* covered, because then a party can make a claim that since it was not explicitly excluded, it is within scope. That is a dangerous legal footing.
Mature change management processes cover multiple types of changes governed by internal processes in addition to aspects of the deliverable spelled out in the contract. A customer may have no say in sub-tier vendor selection for example, but a formal change process is still typically required to revise business commitments and the corresponding documentation.
...
1 reply by Stéphane Parent
Sep 14, 2022 9:28 PM
Stéphane Parent
...
My point, Keith, was when, not what. It’s more about decision points than scope.
Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Sep 14, 2022 7:54 PM
Replying to Keith Novak
...
I disagree with the statement that the contract stipulates everything that requires a change order.
Change processes may affect lower level things such as business documentation invisible to the customer such as the WBS. Legal language typically tries to avoid saying what is *not* covered, because then a party can make a claim that since it was not explicitly excluded, it is within scope. That is a dangerous legal footing.
Mature change management processes cover multiple types of changes governed by internal processes in addition to aspects of the deliverable spelled out in the contract. A customer may have no say in sub-tier vendor selection for example, but a formal change process is still typically required to revise business commitments and the corresponding documentation.
My point, Keith, was when, not what. It’s more about decision points than scope. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Key point is understand what resource mean in your question. For example if as part of your project you have tasks about decomissing infraestructure then you have to create a change in most of the companies. But generally speaking, each time something change in your project and the change will impact in some way the project then you need to create a change. Saving Changes...
My point is that change management is a fundamental element of configuration management which forms the basis for the decision points.
Charters are high level and at most they will cover a subset of project related artifacts under configuration control. Business management systems often include a whole universe of other organizational assets that are under also formal configuration management. When those items are changed, a change record is required. The process can vary widely based on the nature of the change, and can have a huge impact on cost.
The decision points can be related to the product definition, to the business artifacts like schedules, budgets and resource assignment, while yet others might be mundane paperwork changes that still require a formal record by law.
Large companies will have whole teams of experts to decide what type of change requires what type of process if any. Saving Changes...
Community Champion
