Role of stakeholder in requirement elicitation

Save this page for later by
adding it to your bookmarks
Press Ctrl+D (Windows)
or Cmd+D (Mac OS)
Text
Sources

Introduction

A stakeholder refers to an individual who is affected by the systems involved in an object or who has an impact of affecting the project systems in any way. Stakeholders are individuals that define the scope of a project and then provide the necessary input in the course of requirements analysis as well as negotiation and in approve the system into service. The input of stakeholders in a project is essential and as such, keen appropriation of stakeholders is critical for the success of a project (Faulconbridge & Ryan, 2003). Assessment of their needs as well as role in a project system needs carrying out for effective management of project goals and targets.

New elements of stakeholder behavior

Engineering literature entails identification and assessment of the potential risks posed in the event that the relevant stakeholders are not identified. Identification of the relevant stakeholders is essential in ensuring there are no incidents of missed requirements in the scope of a project. Failure to recognize the requirements of stakeholders may result in alterations during delivery of the project or after the delivery of the project. Clear pointing out of stakeholders is prudent in a bid to ensure that there is adequate definition as well as understanding of the stakeholder groups as well as their dynamics regarding shortcomings that may arise in the subsequent design phases (Costantino & Lewis, 2015).

In the background of a specific system development, it is primary to ensure there is a business owner who is answerable for development of the project. The individual ought to have adequate authority to provide direction regarding to management of the project as well as development of the system. In addition, they are required to endorse the management developed by stakeholders to nominate stakeholder representatives as well as to agree on the priorities of stakeholders (Faulconbridge & Ryan, 2003). They are also required to harbor adequate authority to settle any conflict arising among various parties. In the event that an owner of the process is essential for ensuring that there are smooth tradeoffs in the requirements engineering phase. The responsible business owner is referred to as the project champion as a result of a broad range of responsibilities (Cots, 2011).

Conclusion

In conclusion, the view perspectives of stakeholders ought to be taken into consideration for purposes of consolidating plans in the completion of a provided systems engineering effort. None the less it is mutually beneficial to result to sole stakeholders for definition of the scope of the project. Failure to recognize the requirements of stakeholders may result in alterations during delivery of the project or after the delivery of the project (Faulconbridge & Ryan, 2003). Clear pointing out of stakeholders is prudent in a bid to ensure that there is adequate definition as well as understanding of the stakeholder groups as well as their dynamics regarding shortcomings that may arise in the subsequent design phases.

Did you like this sample?
  1. Costantino, C. A., & Lewis, M. R. (2015). What Dispute Systems Design Can Learn from Project Management. Negotiation Journal, 31(3), 175-210.
  2. Cots, E. G. (2011). Stakeholder social capital: a new approach to stakeholder theory. Business Ethics: A European Review, 20(4), 328-341.
  3. Faulconbridge, R. I., & Ryan, M. J. (2003). Managing complex technical projects: A systems engineering approach. Artech House.
Find more samples:
Related topics
More samples
Related Essays