Find out which people, roles, organizational units or organizations have interests in the system.

Description

Get an initial list of stakeholders from project management.

Distinguish between roles and individuals. Some stakeholders need to be addressed individually; for roles it might be sufficient to identify any of several possible representatives.

Take the following list as examples of roles:

top management, business management, project management, product management, process management, client, subject-matter expert, business experts, business development, enterprise architect, IT strategy, lead architect, developer, tester, QA representative, configuration manager, release manager, maintenance team, external service provider, hardware designer, rollout manager, infrastructure planner, infrastructure provider, IT administrator, DB administrator, system administrator, security or safety representative, end user, hotline, service technician, scrum master, product owner, business controller, marketing, related projects, public or government agency, authorities, standard bodies, external service or interface providers, industry or business associations, trade groups, competitors

Include those stakeholders in a simple table:

Role/Name Description Intention Contribution Contact
name of person or role responsibility for the system intention for/with/against the system what they can, will or need to contribute to the improvement, optional or required how to contact; for roles, name a primary contact person

Experience

There are often more stakeholder roles involved than is obvious. Especially people not directly involved in project or development work are sometimes forgotten, e.g. standard bodies, external organizations, competitors, press or media, legal department, employee organization.

References