RAJESH K LProject Manager, PMP| Bharat Electronics, Bengaluru, IndiaBengaluru, Karnataka, India
In case of project scope change, is there a need to
revise Projdct charter? Saving Changes...
Sort By:
Anonymous
Is this change to the project objective or the details?
If a change to the objective, then by default you are changing the charter and whether you revise it, ammend it, or add a change document with it - is up to the organization policies.
If the change in details that does not affect the objective and the change is required to meet the objective, then there is no change to the charter Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
A change into the scope will change everything into your project. Depending on your configuration management/change control/governance system/process you must or not to change the project charter. Saving Changes...
In waterfall, no, unless the sponsor requires it. Otherwise, a new project may be called for. In Agile, bring it on, but something else in scope must give. Saving Changes...
Anonymous
Jun 10, 2018 4:49 PM
Replying to Sante Delle-Vergini, PhD
...
In waterfall, no, unless the sponsor requires it. Otherwise, a new project may be called for. In Agile, bring it on, but something else in scope must give.
Sante,
1. On your first point: I do not understand, since when a scope change will become a new project? What is the source of that information? Or is it an opinion?
2. On your second point: are you saying in an Agile environment we do not need a charter or modify the charter? Also, we do not document changes?
Did I understand you correctly?
...
1 reply by Sante Delle-Vergini, PhD
Jun 11, 2018 7:44 PM
Sante Delle-Vergini, PhD
...
Hey Mounir, long time no hear.
1. I should clarify that a major scope change that requires a change to the project charter can also be handled as a separate project. I think the original question was the impact of scope changes on project charters, and since nearly all scope changed should not impact the project charter, when it does, it usually in my experience leads to another project or what some call an "enhancement".
2. What I am saying is Agile is a lot more accepting of change, hence "bring it on", and since any Agile project charter (that is written correctly) will not require another project regardless of the scope changes that could effect the charter, as it can be modified. Software products do this all the time. I'm not sure where you got "we do not need a charter or modify the charter?" and "we do not document changes?" from what I posted; both are incorrect,
The answer from Sergio is complete. Scope change can change many things and required the Charter to be revisited.
In a rare case, the project may stop and a new project started Saving Changes...
Anonymous
Guys,
we have to be careful here and understand the following. There are different types of changes that could happen on projects, and I am talking about changes to knowledge areas but to the project.
Before we understand change, we must understand the difference between product scope and project scope. Product scope is about what we are producing at the end, the objective. This will be documented in the document that authorizes the project, in the PMI world this is the project charter.
Then we have the project scope; or the work that we must do to deliver the product and per the objectives explained in the charter.
With the above in mind, there are different types of changes:
1. Some changes will be to the project objectives or in the final product. Since this info is in the charter, then these changes would require a revision or amendment to the charter (some organizations do not revise the document but consider a formal change form as the amendment. In these situations, there will be justifications to request an adjustment to the cost and schedule, up or down, depending on the impact of the change.
2. There are changes that might modify the "work" on the project, WITHOUT touching the product scope or the project charter. These do NOT result in a change to the charter and their impact will be part of the project variance.
3. There are changes required because we discovered an error in the early work, and we must do the change IN ORDER TO MEET the original objective of these projects. These are performance matters and DO NOT impact the charter - so NO charter change.
For example, let us say our project is a residential tower that is 10,000 m2 and will have many apartments.
1. If we decide to make this tower 9 or 11 k m2; that is a change in the objective. If we decide to change location, objective change; if we decide to make it smart building instead of a regular building - that is objective. In all of these cases, we would require a change in the charter (or amend) and adjustment to cost & schedule.
2. Same tower, 10 k m2: in the original conceptual design we forgot to include space for mech & elec equipment, or enough space - that is an error and we must fix it. This is a project change but not an objective change (it does not impact the charter).
3. Let us say the same tower, and the same scope, but we decided to make some design changes to the layout or arrangement; this is not a charter change.
I can give more examples from other industries but I think the above is enough for now. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
The charter is drawn up for the project with a problem to be solved, intent, and goals with a high-level scope. Once a detailed requirement plan is finalized it is not uncommon for realizations to be made and additional items or changes to be requested. This does not necessarily change the rationale behind the project. The change management process will help direct the requests as appropriate - Must have(s)? Can the project absorb the impact (cost, schedule, quality)? These are the questions that first should be discussed with the customer to gain a full understanding......you get the point. Unless what is requested is a completely different problem to be solved and is it's own initiative entirely that would warrant its own charter and project. Saving Changes...
1. I should clarify that a major scope change that requires a change to the project charter can also be handled as a separate project. I think the original question was the impact of scope changes on project charters, and since nearly all scope changed should not impact the project charter, when it does, it usually in my experience leads to another project or what some call an "enhancement".
2. What I am saying is Agile is a lot more accepting of change, hence "bring it on", and since any Agile project charter (that is written correctly) will not require another project regardless of the scope changes that could effect the charter, as it can be modified. Software products do this all the time. I'm not sure where you got "we do not need a charter or modify the charter?" and "we do not document changes?" from what I posted; both are incorrect, Saving Changes...
Michael DelaneyPartner| Delaney Management LLCWest Chester, Pa, United States
I also fall into the camp that if the a change requires a charter change is should be a new project. Although if the change is more of a clarification or enhancement to the charter then it could be accommodated, although you would need to update all aspects of the plan, Saving Changes...
