This document defines and describes different types of stakeholders. It discusses product, project, and process stakeholders. Product stakeholders include suppliers (developers and distributors) and acquirers (customers and users). Project stakeholders include those funding, initiating, supporting, or on the project team. Process stakeholders affect or are affected by a process. The document emphasizes the importance of identifying stakeholders, prioritizing them, determining their participation, and understanding their needs and motivations.

1. Customers and Other
Stakeholders
Topic 6.2
Topic Covered
 Stakeholder and it types

2. Stakeholders
Stakeholders are individuals or groups who affect or are
affected by a software product, project, or process and
therefore have some level of influence over the
requirements for that software product, project, or process.

3. Product Stakeholders
These have three main categories
1. the suppliers of the software
2. the acquirers of the software
3. and other stakeholders

5. 1. suppliers of the software
 The suppliers of the software include developers and distributors.
 Developers
The individuals and groups that are part of the organization that
develops and/or maintains the software
 Distributors
The individuals and groups that distribute the software.

6. 2. acquirer-type stakeholders
The acquirer-type stakeholders can be divided into two major groups.
1. First there are the customers who select, request, purchase, and/or pay for
the software in order to meet their business objectives.
2. The second group is the users who actually use the software directly or use
the software indirectly by receiving reports, outputs, or other information
generated by the software.

7. 2. acquirer-type stakeholders
Users have different types. For example,
 there may be novice users, occasional users, and power users of a software
product.
 There may also be users with different levels of knowledge or skill, different
roles or objectives, different access privileges, or different motivations.
 For example, some of the users of a “pay at the pump” system include the
manager of the gas station, the attendant, car owners purchasing gas,
eighteen-wheeler drivers, credit card thieves, people with expired credit
cards, illiterate people, and people that don’t speak English. Each of these
stakeholder groups may place different requirements on the software.

8. 3. Other Stakeholders
 Other stakeholders that don’t belong to either the supplier or acquirer groups
but still may have some level of influence over the software include:
1) Lawmakers or regulatory agencies that create laws, regulations, and
standards that impact the software product
2) Organizations that create industry standards or guidelines or define industry
best practices for the software product
3) Other groups or individuals that are impacted by the actions or decisions of
the product’s acquirers or suppliers
4) Even society at large can have a vested interest in the software

9. Project Stakeholders
 The Project Management Institute (PMI) (2008) defines
project stakeholders as
“persons and organizations that are actively involved in the
project, or whose interests may be positively or negatively
affected by the execution or completion of the project.”

10.  Project stakeholders include the individuals funding,
initiating, and/or championing the project, customers of
the project, or individuals supporting the project, as well
as anyone on the project team and the stakeholders of
the products produced by that project.
 Project stakeholders may also include individuals from
other projects or programs that must interface or
coordinate with the project (for example, other projects
in the same program or individuals in the project
management office).

11. Process Stakeholders
Process stakeholders are individuals who affect or are
affected by a software process or its outcome.

12.  Process stakeholders include the individuals funding the
process activities, defining, documenting, and
improving the process, or championing the process, as
well as anyone directly involved in the execution of the
process activities or steps and the stakeholders of the
products produced by that process.
 Process stakeholders may also include individuals from
other processes that must interface or coordinate with
the process, as well as individuals responsible for auditing
or assessing the process.

13. Benefits of Identifying and Involving
Stakeholders
 Identifying and considering the needs of all of the different
stakeholders can help prevent requirements from being overlooked
 Identifying and involving key stakeholders provides access to the
stakeholder’s experience base and domain knowledge
 Identifying the different stakeholders and getting them involved also
brings different perspectives to the table that can aid in a more
complete view of the work to be accomplished.

14.  Many people are uncomfortable with and therefore resist
change.
 Involved stakeholders are more likely to buy in to the
completed work, which can create “ownership” and make
them champions for the change within their stakeholder
community.
 This can be beneficial in the transition of the new
product, process, or project into the stakeholder’s
environment.

15. Stakeholder Participation Plans
 We can't consider needs of all the stakeholder while we
will be in development phase.
 The needs of stakeholders may also contradict or conflict
with each other.
 So, Prioritize the stakeholders

16.  Once all of the stakeholders have been identified, the
first-level cut at this prioritization is to sort those
stakeholders into categories of:
 Must include—this stakeholder must be included
 Like to include—this stakeholder will only be included if
time allows
 Ignore—this stakeholder will not be directly included

17.  For each stakeholder group that is included, a decision
must be made about who will represent that stakeholder
group in the product, process, or project activities. There
are three main:
1) Representative
2) Sample
3) Exhaustive

18.  The second decision is to determine when and how each
included stakeholder group needs to participate in the
activities.
 Which activity and how much time for participation?
 The final decision is to establish the second level of
priority of each included stakeholder group based on their
relative importance to the success of the software
product, process, or project.
 As conflicts arise between the needs of various
stakeholders, priorities help determine whose voice to
listen to.

19. Stakeholder Needs and Motivations
 Stakeholders needs and motivations must be identified
and understood for a product, process, or project to be
successful.
 Method
 meet with each stakeholder
 Encourage through open communication
 sharing of both positive and negative perspectives of the
product, process, or project.

20.  Stakeholders needs:
 Can be easily identify (commonly acknowledged
business needs).
 Can be hidden agendas (unacknowledged motives)
 All these needs to be uncovered and understood.

21. THANK
YOU