Frances KerrAssociate Program Manager| PreSonus Audio ElectronicsBaton Rouge, La, United States
I agree with others here that Identify Stakeholders is an iterative process, but unless you initiate the project yourself, a PM will need to Identify them before creating a charter. Saving Changes...
Who is the responsible person to ensure that all potential stakeholders are identified in "identify stakeholders" process? If your answer is "Project Manager" , then "develop project charter" comes first so that authorize the project manager to a project. Saving Changes...
Mohammad KhanDeputy Vice President, Program Management| MetLife BangladeshDhaka, Bangladesh
Aug 15, 2017 4:13 PM
Replying to Anthony Barreras
...
Without the project charter you don't really know who the stakeholders are. Yes, there is often some semblance of a scope floating around on something that a business uses to continue the conversation in the very beginning of a project's lifecycle but realistically you can't get anyone on the same page without writing down the idea and why (initial business case) it should be done, essentially the draft of a project charter. once you have this draft then you can ask who will be impacted hence the identifying of stakeholders. You should not assign a PM with a blank page in your hand as a portfolio manager or a project sponsor. You need really need something in the works to get the support and momentum that will be needed to birth a project and assign the project manager. Yes, the PM will often be nearby helping in this process and finalizing the Charter but identifying stakeholders is a far reaching activity that requires more definition than a charter may provide. Just my two cents...
Hi Anthony,
I do disagree with you.
When a project is being initiated you know there is at least one stakeholder, apart from the sponsor, who will be impacted by the project. For example, if you are initiating a technological or process improvement project for HR department, then HR department is the major stakeholder identified although the project charter is not created yet. Saving Changes...
Mohammad KhanDeputy Vice President, Program Management| MetLife BangladeshDhaka, Bangladesh
Aug 16, 2017 1:43 PM
Replying to Eric Simms
...
Without a well-defined charter you won't know for sure which stakeholders you'll need.
Hi Eric,
I do disagree with you.
When a project is being initiated you know there is at least one stakeholder, apart from the sponsor, who will be impacted by the project. For example, if you are initiating a technological or process improvement project for HR department, then HR department is the major stakeholder identified although the project charter is not created yet. Saving Changes...
Product Operations Program ManagerBarcelona, Cataluña, Spain
A Project Charter comes first, since is the first natural step to crystalize an idea into a project. When someone composes a charter he or she typically has in mind who the project stakeholders will be. So, one could argue that stakeholder register could, if really necessary, be written first. However, there is little value in doing so, plus there is the risk that some stakeholders might be forgotten given the lack of a clear on paper project scope.
...
1 reply by Mohammad Khan
Dec 10, 2019 6:33 AM
Mohammad Khan
...
That's why project stakeholder identification is not an one time activity. It is performed throughout the project. But initial identification occurs prior or at the same time of project charter creation.
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de GestĂ£o, LdªCarcavelos, Lisboa, Portugal
Dear George
Interesting your question
Thanks for sharing
There are two processes in the initiation process group.
Project Charter and Stakeholder Identification which, if properly analyzed, can be a high level risk Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The key point here is: if you are talking about project management then what you must identify is project stakeholders. You are not assigned to a project until the project charter is created and approved then project charter is first, is nothing to do about project stakeholders because there is not project. Here is when a role mostly forgotten has to be taken into account: business analyst. Business analyst performs stakeholders identification before a project exists because business analyst work before a project exists, along the project and when the project is close business analyst continue working to meassure benefits. What project manager must do is taken the stakeholder analysis done by the business analyst and add the project stakehodler analysis to it.
...
1 reply by George Lewis
Dec 10, 2019 6:52 AM
George Lewis
...
Bingo Luis...
Saving Changes...
Mohammad KhanDeputy Vice President, Program Management| MetLife BangladeshDhaka, Bangladesh
Dec 10, 2019 4:02 AM
Replying to Eduard Hernandez
...
A Project Charter comes first, since is the first natural step to crystalize an idea into a project. When someone composes a charter he or she typically has in mind who the project stakeholders will be. So, one could argue that stakeholder register could, if really necessary, be written first. However, there is little value in doing so, plus there is the risk that some stakeholders might be forgotten given the lack of a clear on paper project scope.
That's why project stakeholder identification is not an one time activity. It is performed throughout the project. But initial identification occurs prior or at the same time of project charter creation. Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
Dec 10, 2019 5:09 AM
Replying to Sergio Luis Conte
...
The key point here is: if you are talking about project management then what you must identify is project stakeholders. You are not assigned to a project until the project charter is created and approved then project charter is first, is nothing to do about project stakeholders because there is not project. Here is when a role mostly forgotten has to be taken into account: business analyst. Business analyst performs stakeholders identification before a project exists because business analyst work before a project exists, along the project and when the project is close business analyst continue working to meassure benefits. What project manager must do is taken the stakeholder analysis done by the business analyst and add the project stakehodler analysis to it.
Bingo Luis... Saving Changes...
George LewisProgram/Project Manager| DXC Technology CompanyHeredia, Costa Rica
Thanks for your comments, but unless we factor the Business Analyst in all this, there is no proper response.
If we are talking about project management Project Charter comes first and Stakeholders Identification comes next.
Here is the catch, of course, the PM name (a key stakeholder) comes within the project charter which means someone had to figure out that and other names (other key stakeholders), but these initial names by definition (with no doubt at all) pre-dates the project itself, ie pre-dates the project charter, thus performed with some other magic process which we normally forget that exists: Business Analysis.
...
1 reply by Sergio Luis Conte
Dec 10, 2019 7:33 AM
Sergio Luis Conte
...
That´s what I try to said. Project Charter comes first because the project manager is assigned when the Project Charter is approved. In the real life, you can find lot of different process. For example, assigned project manager and the sponsor is included into the Business Case document most of the times. The point is, there is not an standard for project charter neither for business case as you can find for other documents (i am talking about IEEE standards or similar recognized standards).