Prashant ShelkeSenior General Manager| Brookfield Properties410 210, Maharastra, India
Stakeholder analysis in conducted to ensure all the requirements are gathered as well as also to study the individual stakeholder influence on the project .
In the Change management , sometime a committee is been set up wherein the changes are getting approved by the committee .
In one of the scenario , Changes were been approved by the Project manager appointed by the Client ,but at a later stage of the project the CEO comes into pictures and disapproves the Change request already approved by their PM .
What are the precautions that needs to be taken to avoid such situations?
Where the same needs to be captured ?
.Is there any standard format for the same? Saving Changes...
I am assuming you are a contractor. In that case, what does the contract says? Does the contract specific who can issue change order or instruction to the contractor? If yes, you follow the contract. If not, then maybe you have the basis for a claim.
...
2 replies by Prashant Shelke
Nov 23, 2017 4:11 AM
Prashant Shelke
...
No I am not a contractor ,the scenario that had been described were one of the lessons learnt and hence felt to put the forum for better insights for proactive actions
Nov 23, 2017 4:12 AM
Prashant Shelke
...
No I am not a contractor ,the scenario that had been described were one of the lessons learnt and hence felt to put the forum for better insights for proactive actions.
The scenario was during the tenure of the project -Change orders were approved by the PM and it was been communicate that the same has been approved internally within their team from the Client .But later on it came as a surprise in a Management review meeting that No Changes are approved .Managment Level meetings happened in 6 to 8 months .
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Sorry if I misunderstood but there is a mix into your statement. First of all we need to understand that one thing is organizational change and other thing is project change. Second, project manager NEVER must approve changes. The duty of project manager is to run the project change management process to assure that all needed are in hands of the people that must approve changes. Third, you have to take into account two type of requirements: project requirements and product requirements. The first one is on charge of project manager. The second one on charge of the business analyst.
...
1 reply by Prashant Shelke
Nov 23, 2017 4:22 AM
Prashant Shelke
...
It was briefed to our team that PM representing the Client would be the single point of contact and everything has to be through him .Though there were weekly reports which were circulated in which the change order status report was also been published .
I am very sorry if my way of putting across my question or view point was perceived differently .
This was one of my first post in this forum ,but yes I am happy that I put it across .learning so great things from all the professionals in this network .
You cannot avoid these situations. They are a fact of professional life.
We make decisions based on what information we have and our domain of responsibility.
The CEO has much more information at her disposal and a much bigger domain of responsibility.
You should treat the CEO's decision as a project constraint. Saving Changes...
Anonymous
Nov 22, 2017 8:37 AM
Replying to Sergio Luis Conte
...
Sorry if I misunderstood but there is a mix into your statement. First of all we need to understand that one thing is organizational change and other thing is project change. Second, project manager NEVER must approve changes. The duty of project manager is to run the project change management process to assure that all needed are in hands of the people that must approve changes. Third, you have to take into account two type of requirements: project requirements and product requirements. The first one is on charge of project manager. The second one on charge of the business analyst.
Sergio
I have worked for global organizations where the PM/PD has the power to approve changes and it worked well. Do not consider all changes to be the same.
...
1 reply by Sergio Luis Conte
Nov 22, 2017 9:17 AM
Sergio Luis Conte
...
My too, but is the worst thing you can do. I will say way: the project manager do not have the whole picture. And the stakeholders owns the project and all that happens on the project. At the end, I agree with you that each organization has its own dynamic. But from years ago I always push for the same: all changes are welcome if and only if we agree that stakeholders own the changes.
Saving Changes...
Anonymous
Prashant
It is clear that three responses here - each of us understood the scenario in a different way. So you need to re-clarify the question Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
My too, but is the worst thing you can do. I will say way: the project manager do not have the whole picture. And the stakeholders owns the project and all that happens on the project. At the end, I agree with you that each organization has its own dynamic. But from years ago I always push for the same: all changes are welcome if and only if we agree that stakeholders own the changes. Saving Changes...
Anonymous
Nov 22, 2017 9:17 AM
Replying to Sergio Luis Conte
...
My too, but is the worst thing you can do. I will say way: the project manager do not have the whole picture. And the stakeholders owns the project and all that happens on the project. At the end, I agree with you that each organization has its own dynamic. But from years ago I always push for the same: all changes are welcome if and only if we agree that stakeholders own the changes.
Sergio
We can have a separate thread on this since we are not aligned on this topic and the definition of change.
Quickly:
There are project changes - that DO NOT impact the objectives
Contract changes - same as above
Objectives changes
The first two are best handled by PM
The last one by Sponsor/Project Executives/Steering Committee
...
1 reply by Sergio Luis Conte
Nov 22, 2017 4:14 PM
Sergio Luis Conte
...
Each change must impact into project objectives to be a project change. If not, it has no sense to be consider a change by definition.
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Each change must impact into project objectives to be a project change. If not, it has no sense to be consider a change by definition. Saving Changes...
Anonymous
Nov 22, 2017 4:14 PM
Replying to Sergio Luis Conte
...
Each change must impact into project objectives to be a project change. If not, it has no sense to be consider a change by definition.
Every change could have an impact? Yes
Every change is an objective change? No
Let us have a different thread on this Saving Changes...
This is part and parcel of the job.
First we need to identify the stake holders roles and responsibility.
In addition to that approval level also identified and route the change/requirement accordingly to avoid last minute surprises.
Normally changes / requirement approval is having two hands one - business approval, second - cost / time line approval. Saving Changes...
