IEEE Software
Stakeholder Identification in the Requirements Engineering Process
DEXA '99 Proceedings of the 10th International Workshop on Database & Expert Systems Applications
Risk Management during Requirements
IEEE Software
Understanding Project Sociology by Modeling Stakeholders
IEEE Software
StakeNet: using social networks to analyse the stakeholders of large-scale software projects
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Stakeholder collaboration and engagement in virtual projects
International Journal of Networking and Virtual Organisations
Proceedings of the ACM-IEEE international symposium on Empirical software engineering and measurement
| Hi-index | 0.00 |
Requirements engineering must manage the risks arising from project stakeholders. The Outcome-Based Stakeholder Risk Assessment Model (Obsram) provides guidance in stakeholder identification, identification of stakeholder impacts and perceptions, identification of potentially negative responses that pose risks to the project, and assessment and prioritization of those risks. This information provides valuable input to a risk mitigation plan that let you devote more resources and attention to the stakeholders that pose the greatest risk to your project. A case study offers a practical, step-by-step approach to this process. This article is part of a special issue on stakeholders in requirements engineering.