Hi Michael, this is such a difficult question with more than one answer. I prefer to think that both could identify stakeholders in a colaborative way. Along the process one or the other will work more on this task. But I agree with some collegues that the PM is accountable for it in the project environment.
TAKE INTO ACCOUNT: the new name of the process inside the PMBOK is "Project Stakeholder Management".First, the best thing you can do to answer this question is to go to the PMI´s Practitioners Gude for Business Analysis and read the "Collaboration Point" section. Second, we need to undestand that all depends on the process you use to do things. The business analyst is accountable to help the organization to create the solution to business need. Solution is equal to "the thing" (product/service/result) to be created PLUS "the process" (project) to create it. Becuse of that the business analyst start working where nothing than a need exists. At this time, the business analyst will start the whole stakeholder management process focused in solution. One of these stakeholders will be the project manager that could be assigned to the project.
Hello Sergio. Great point. This is my thought also because the BA starts early even before the PM is assigned so he'she will identify the stakeholders first then as the PM gets involved both of them can expand that circle based on the needs and work together in managing it. I also thin the BA deals more with enterprise needs while PM focuses with Project needs. This my apply differently based on the project methodology and business system. Saving Changes...
Greg FabianRetired IT Project/Program Manager and Technology Strategist| RetiredFairfax Station, Va, United States
I'll take a slightly different tack and say that the program manager is actually responsible for identifying the stakeholders - that is if you project is part of an over-arching program. Ideally, your PM's, when operating in the context of a program, should already have a clear understand of who the stakeholders are. But not all organizations operate this way. Saving Changes...
Abdulilah AngaaCrowne Plaza Project Manager (Riyadh)| RIDCORiyadh, Saudi Arabia
Stakeholders identification is not one time activity, and the stakeholders register log is updated continuously throughout the project life, and it is PM responsibility to update that log, but in many cases the PM is not selected until the project initiation completed, and that case someone should take the lead and for sure the BA is the best one to handle the matter.
...
2 replies by Rolf Dieter Zschau and Thomas Walenta
May 04, 2016 4:21 AM
Thomas Walenta
...
agree.
May 04, 2016 7:48 AM
Rolf Dieter Zschau
...
Agree. And add: PM is responsible for project (or program) context, BA for enterprise context. So both are working on it throughout their assignment. For project (program) PM is responsible, for overall enterprise context BA is responsible. This sounds weird but works very well. Each of them identifies stakeholders and communicates to the other. Each of them has a different view on stakeholders, so they add value to a single view. In case of conflicts, there are numerous methods to solve conflict. (There is usually more than one project during the lifetime of a "thing", so more than one PM may be involved - and maybe also more than one BA)
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
May 04, 2016 2:17 AM
Replying to Abdulilah Angaa
...
Stakeholders identification is not one time activity, and the stakeholders register log is updated continuously throughout the project life, and it is PM responsibility to update that log, but in many cases the PM is not selected until the project initiation completed, and that case someone should take the lead and for sure the BA is the best one to handle the matter.
Stakeholders identification is not one time activity, and the stakeholders register log is updated continuously throughout the project life, and it is PM responsibility to update that log, but in many cases the PM is not selected until the project initiation completed, and that case someone should take the lead and for sure the BA is the best one to handle the matter.
Agree. And add: PM is responsible for project (or program) context, BA for enterprise context. So both are working on it throughout their assignment. For project (program) PM is responsible, for overall enterprise context BA is responsible. This sounds weird but works very well. Each of them identifies stakeholders and communicates to the other. Each of them has a different view on stakeholders, so they add value to a single view. In case of conflicts, there are numerous methods to solve conflict. (There is usually more than one project during the lifetime of a "thing", so more than one PM may be involved - and maybe also more than one BA) Saving Changes...
Patrick DiceyManager, Customer Project Management| CentralSquare TechnologiesOrlando, Fl, United States
Apr 14, 2016 9:32 AM
Replying to John Herman
...
THE ENTIRE PROJECT IS THE RESPONSIBILITY OF THE PM. The PM must own the project from the time they are assigned until the project achieves closure.
I agree with you John. The PM is responsible for all scope/processes (including stakeholder management). Responsibilities can certainly be delegated to a BA, as appropriate, if one exists on the project team. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
We need to understand that there are two key roles. And we need to understand that, depending of the life cycle you use, there are two key phases to create a soltuion: pre and post project phase and project phase. For Pre and post project phases the business analyst is accontable for. Project phase the project manager is accountable for. But about responsability all the stakeholders involved into solution process are responsible. Solution is equal "the thing" (product/process/result) to be created plus "the process" (project) to create it. Business analyst and project manager are both roles as you know. But it is key to understand the solution scope to not fail. NOTE: I am using "accountable" and "responsible" terms as those are used in RACI jargon.
...
1 reply by Rolf Dieter Zschau
May 06, 2016 1:22 AM
Rolf Dieter Zschau
...
This text is like a reference text book, but I second it completely.
We need to understand that there are two key roles. And we need to understand that, depending of the life cycle you use, there are two key phases to create a soltuion: pre and post project phase and project phase. For Pre and post project phases the business analyst is accontable for. Project phase the project manager is accountable for. But about responsability all the stakeholders involved into solution process are responsible. Solution is equal "the thing" (product/process/result) to be created plus "the process" (project) to create it. Business analyst and project manager are both roles as you know. But it is key to understand the solution scope to not fail. NOTE: I am using "accountable" and "responsible" terms as those are used in RACI jargon.
This text is like a reference text book, but I second it completely. Saving Changes...
Safi ullah MohammedProject Management/ Constrcution Management| Vision International InvestmentJeddah, Saudi Arabia
Identifying stakeholders close relates to business analyist, wheras meeting the expectations goes to project manager. Saving Changes...
