For each product or system, the different stakeholders (= interest groups) can be identified from these.<\/p>\n
Product life cycle<\/h3>\n
![\"\"](\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/product_life_cycle-1024x292.png\")
<\/p>\n
Item life cycle<\/h3>\n
![\"\"](\"http:\/\/p4dev.hardscrum.com\/wp-content\/uploads\/sites\/3\/2019\/08\/unit_life_cycle-1024x311.png\")
<\/p>\n
The P4 framework distinguishes between three groups of stakeholders, which are assigned to the three areas<\/p>\n
- \n
- Market & Business<\/a>: users, customers and sales<\/a><\/li>\n
- Technology & Architecture<\/a>: suppliers, supply chain & production<\/a><\/li>\n
- Infrastructure & Processes<\/a>: managers of other areas of the organisation<\/a><\/li>\n<\/ul>\n
Other stakeholders<\/h2>\n
In addition to the “direct” stakeholders, other, “more general” stakeholders are usually defined in requirements management. These are, for example<\/p>\n
- \n
- the society, consisting of public and government organizations<\/li>\n
- the environment (mostly affected by emissions and waste)<\/li>\n
- competitors<\/li>\n<\/ul>\n
In the P4 framework, these stakeholders are not represented by Stakeholder Needs, but by specific goals (e.g. to describe the competitive situation) or they are represented by norms and standards in the area of Quality Attributes & Constraints (QA&C)<\/a>.<\/p>\n
Stakeholder map<\/h1>\n
A Stakeholder map shows the various stakeholders with their needs and the strength of their influence on the team or system.<\/p>\n
.<\/span><\/p>\n
\nFurther suitable links:<\/p>\n
- \n
- Definition on Wikipedia: Stakeholder<\/a><\/li>\n<\/ul>\n
- Technology & Architecture<\/a>: suppliers, supply chain & production<\/a><\/li>\n