Explanation/Reference:
Explanation:
5.2.1.5 Stakeholder Register
Described in Section 13.1.3.1. The stakeholder register is used to identify stakeholders who can provide information on the requirements. The stakeholder register also captures major requirements and main expectations stakeholders may have for the project.
13.1.3.1 Stakeholder Register
The main output of the Identify Stakeholders process is the stakeholder register. This contains all details related to the identified stakeholders including, but not limited to:
Identification information. Name, organizational position, location, role in the project, contact
information;
Assessment information. Major requirements, main expectations, potential influence in the project,
phase in the life cycle with the most interest; and
Stakeholder classification. Internal/external, supporter/neutral/resistor, etc.
The stakeholder register should be consulted and updated on a regular basis, as stakeholders may change-or new ones identified-throughout the life cycle of the project.
Process: 5.2 Collect Requirements
Definition: The process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Key Benefit: The key benefit of this process is that it provides the basis for defining and managing the project scope including product scope.
Inputs
1. Scope management plan
2. Requirements management plan
3. Stakeholder management plan
4. Project charter
5. Stakeholder register
Tools & Techniques
1. Interviews
2. Focus groups
3. Facilitated workshops
4. Group creativity techniques
5. Group decision-making techniques
6. Questionnaires and surveys
7. Observations
8. Prototypes
9. Benchmarking
10.Context diagrams
11.Document analysis
Outputs
1. Requirements documentation
2. Requirements traceability matrix
