Manage Stakeholders List

SK51
Tera Contributor

How does everyone manage the stakeholder register list? 

We maintain a list of stakeholder based on portfolio. 
however when demand manager/ project manager add a new stakeholder to their demand/ project, the new stakeholder is rolled up and saved at portfolio stakeholder register..

1) How can we avoid the addition of new stakeholder from demand/ project roll up to portfolio level? 

2) What is your practice of maintaining the stakeholder register at portfolio level?

 

thanks. 

1 ACCEPTED SOLUTION

Mamta9
Tera Expert

 

 

 

 

Hi SK,

 

There is a way to prohibit rolling up of stakeholders on Portfolio level?

There is a business rule written on dmn_demand table which does the entry into stakeholder register.

You can disable this business rule-

 

find_real_file.png

 

Its upto every organisation how do they want to maintain the list. Our org does a half yearly review of the register and removes not needed stakeholders.  Addition is a continuous activity.

 

Regards,

Mamta 

View solution in original post

6 REPLIES 6

Rae Ann Prasnic
ServiceNow Employee
ServiceNow Employee

Stakeholders to ServiceNow are used for two things: Approvals and Assessments. 

Often demand and project managers want a list of TEAM members - which is not what Stakeholders is for and ServiceNow does not offer a related list for tracking OOTB. 

As Mamta suggested, you can make changes to the business rule so it doesn't roll up. You can also clean it up on a regular basis. But you can also tell your demand and project managers to keep their fingers off stakeholders and ask your ServiceNow team to add a "Team Member" related list to give your users what they want. 

Hope this helps, Rae Ann

Would you or any other SPM SMEs be able to elaborate on this proposed solution?  Is @Rae Ann Prasnic suggesting that a custom related table be created called "Team Members" or is there an out of box "Team Members" related list available that can be exposed?

 

Based on this explanation I would suggest that:

  1. ServiceNow instead rebrand the current Stakeholder related list in SPM (Demands and Projects) to "Approvers."
  2. ServiceNow expose a new related list specific for Stakeholder Registry in PMI alignment.  The format as presented today is great, but would need to create a 1:many relationship to enable any given stakeholder to map to multiple demands/projects each with their own individual scores/answers per SPM artifact (not portfolio centric).