Focusing on Delivering Stakeholder Value
[ Execution time: 0.45 secs ] [ Memory usage: 15.37MB ] [ 58 database queries used in 0.0 secs ] [ Server load: 1 ]
| Name | Stakeholder Value | ||
| Concept Number | |||
| Definition |
the values/how-well/improvements/qualities the Stakeholders needs or desires for themselves or to do their business. |
||
| Examples |
Sale.Paperwork Scale: average time spent, per sale, doing paperwork related activities. Meter: look it up in the time management tool. Past [2004] 2 hours. Goal [2006] 15 minutes. see Scale db for an extensive list of examples. |
||
| Notes |
Stakeholder Values are the scalar improvements a Stakeholder need or desire. Product Qualities are the scalar attributes of a Product. Stakeholder Level Values, Functions, Development Resources, Solution Constraints. Product Level Qualities, Functions, Development Resources, Solution Constraints. A Stakeholder would normally have their Stakeholder Values, irrespective of the product you are developing. It relates to how well they do, or their business do. Your product, with its Product Qualities (e.g. Usability), can become the Solutions to satisfy a Stakeholder Value. A product could be developed with Functions and Product Qualities to satisfy Stakeholder Values. A Stakeholder Values is 'attached' to Stakeholders. A Product Quality are 'attached' to a product. |
||
| Illustration |
|
||
| Related Concepts |
Stakeholders, Product Qualities, Levels, Stakeholder Level. |
||
| Synonyms | |||
| Language Name Variants | |||
| Submitted | Kai Thomas Gilb | ||
| Editor | Kai Thomas Gilb | ||