In simple words, anyone having any type of relation/interest in the project is known as stakeholder. The term Software Project Stakeholder refers to, “a person, group or company that is directly or indirectly involved in the project and who may affect or get affected by the outcome of the project”.
What is Stakeholder Identification?
It is the process of identifying a person, group or a company which can affect or get affected by a decision, activity or the outcome of the software project. It is important in order to identify the exact requirements of the project and what various stakeholders are expecting from the project outcome.
Type of Stakeholders:
1. Internal Stakeholder:
An internal stakeholder is a person, group or a company that is directly involved in the project.
- Project Manager:
Responsible for managing the whole project. Project Manager is generally never involved in producing the end product but he/she controls, monitors and manages the activities involved in the production.
- Project Team:
Performs the actual work of the project under the Project Manager inluding development, testing, etc.
Organisation who has taken up the project and whose employees are directly involved in the development of the project.
Provides funds and resources for the successful completion of the project.
2. External Stakeholder:
An external stakeholder is the one who is linked indirectly to the project but has significant contribution in the successful completion of the project.
Specifies the requirements of the project and helps in the elicitation process of the requirement gathering phase. Customer is the one for whom the project is being developed.
Supplies essential services and equipment for the project.
Makes policies which helps in better working of the organisation.
- Software Engineering | Project size estimation techniques
- Types of Software Testing
- Software Testing | Basics
- Software Engineering | Architectural Design
- Software Engineering | Halstead’s Software Metrics
- Beta Testing | Software Testing
- Software Engineering | Debugging Approaches
- Pairwise Software Testing
- Software Engineering | COCOMO Model
- Software Engineering | Classification of Software Requirements
- Software Engineering | Classical Waterfall Model
- Software Engineering | Iterative Waterfall Model
- Software Engineering | Spiral Model
- Software Engineering | Requirements Engineering Process
- Software Engineering | Requirements Elicitation
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.