Versions Compared

Old Version 3

changes.mady.by.user Patricia Sheppard

Saved on

compared with

New Version 4

changes.mady.by.user Karon S McCollin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

For a more in depth analysis of stakeholders template, click here: Identify Stakeholders 202.docx

Why do Stakeholder identification, analysis and engagement?  

 A stakeholder analysis can help a project identify:

 • Interests of all stakeholders who may affect or be affected by the project

• Potential conflicts or risks that could jeopardize the project

• Opportunities and relationships that can be built on during implementation

• Groups that should be encouraged to participate in different stages of the project

• Appropriate strategies and approaches for engagement

 

Remember: A stakeholder is any entity, internal or external, who could directly or indirectly affect your project or be affected by your project.

Steps:

Panel
  1. Identify: Facilitate interviews of project sponsor, business owner and users using checklist below
  2. Analyze and Understand: Document the information and analyze Stakeholders based on role and desired level of involvement
  3. Engage: Develop and execute communication strategy for each type of stakeholder based on level of involvement

Checklist: Questions for the Interview

A checklist of questions to ask interviewees in order to identify project stakeholders and their interests.  It’s important to ask all potential stakeholders the relevant questions so you can better analyze their level of interest.

  1. Who will be affected by the success or failure of the solution?
  2. Who is the sponsor---the funder of the project?
  3. Who will receive reports and other output from the solution?
  4. Who is the customer---the user of the end product or service?
  5. What regulatory bodies and standards must the solution and project comply with?
  6. Who will test the solution?
  7. Who will maintain the solution once it is deployed?
  8. Who will build and maintain the hardware and server environments?
  9. Who will support the users and the solution once it is installed (Service Desk, DITR, etc.)?
  10. Who will train on the solution?
  11. Who will be adversely affected by in the project’s area of influence?
  12. Who can best assist with the early scoping of issues and impacts
  13. Who strongly supports the changes that the project will bring?
  14. Whose opposition could be detrimental to the success of the project?
  15. Who is it critical to engage with first, and why?