According to the PMBOK® Guide and the Standard for Project Management, the Stakeholder Register is the specific input to the Collect Requirements process used to identify which stakeholders are capable of providing detailed information regarding project and product requirements.
As per PMI standards, the Collect Requirements process is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives. The Stakeholder Register is essential here because:
Identification: It contains the list of all identified stakeholders who may have an interest in or impact on the project.
Requirement Sources: It helps the project team identify " key " stakeholders who can provide information about specific requirements, including their expectations and their level of influence.
Categorization: It allows the project manager to target specific groups (e.g., end-users, sponsors, or regulators) for requirement-gathering sessions like interviews or focus groups.
The other options are incorrect based on the following PMI document definitions:
Scope management plan: This is a Planning document that describes how the scope will be defined, developed, monitored, controlled, and verified. It provides the process for collecting requirements but does not list the people (stakeholders) themselves.
Stakeholder management plan: (Now often called the Stakeholder Engagement Plan) This document identifies the management strategies and actions required to effectively engage stakeholders. While it uses the register as an input, its focus is on engagement strategy rather than being the primary list used to pull requirement sources.
Project charter: The charter is an input to Collect Requirements because it provides the high-level project description and high-level requirements. However, it does not provide the granular list of stakeholders needed to extract detailed functional or technical requirements.
As per the PMI Lexicon of Project Management Terms, the Stakeholder Register is a living document that ensures the project team remains aligned with the individuals whose needs define the project ' s success.
