Focusing on Delivering Stakeholder Value
[ Execution time: 0.53 secs ] [ Memory usage: 15.99MB ] [ 58 database queries used in 0.0 secs ] [ Server load: 0.95 ]
| Name | Stakeholders | ||
| Concept Number | |||
| Definition |
the critical parties and products with an interest in our project. Any person, group of people, or product that has or we want to have an interest in our project should be considered Stakeholders. |
||
| Examples |
Stakeholder: End-User.Bank-Customer: Stakeholder: End-User.Music-Lover: Pleasure, Beauty, Choice, Stakeholder: End-User.Lake "or the people interested in the lake": Oxygen, Algae, Bio-Diversity, Chemicals. Stakeholder: Customer.Bank: Profit, Happy-Customers Stakeholder: Customer.Music-Stereo-Developer: Market-Share, Reputation, Return-On-Investment Stakeholder: Customer.Lake-Environmentalists: Learning, Happiness, Challenges, Public-Awareness |
||
| Notes |
It is critical to identify the Stakeholders as they have the Requirements that our project potentially shall satisfy. We can group Stakeholders or split one Stakeholder into two or more Stakeholders. For example, if we have two types of End Users, we could specify them together if they have similar Requirements or separately if they have different Requirements. I examine each Stakeholder, and identify: 1) what each one want to achieve, and 2) what we or our system can do to help them achieve it. 3) if we want to be in the business of meeting their needs. |
||
| Illustration |
|
||
| Related Concepts |
Requirements, Stakeholder Values, Stakeholder Function, Stakeholder Level. |
||
| Synonyms | |||
| Language Name Variants | |||
| Submitted | Kai Thomas Gilb | ||
| Editor | |||