According to the PMBOKGuide (specifically the Identify Stakeholders and Develop Project Management Plan processes), the Stakeholder Register is the primary project document used to record all individuals, groups, or organizations that have an interest in, or can influence, the project.
* Why Choice A is correct: During the planning phase, the Project Manager performs a stakeholder analysis to identify who possesses the specialized knowledge or expertise (Expert Judgment) required for specific project activities. In the case of a highly technical project like a " driverless vehicle, " the specific SMEs needed for data analysis should have already been identified, categorized, and documented in the Stakeholder Register with their specific roles and areas of expertise noted. This ensures that the workshop is populated by people whose skills have been vetted as relevant to the project ' s unique technical requirements.
* Analysis of other options:
* B (Senior experts with high status): Academic status does not always equate to project-specific relevance. While they may be experts, if they are not relevant to the specific prototype ' s data or the organization ' s goals, they may not be the right fit.
* C (Major stakeholders nominated by the sponsor): Sponsors often nominate high-level stakeholders (executives), but these individuals may lack the deep technical expertise required to
" analyze data received from the prototype. "
* D (Usual review participants with certifications): Having a certification does not automatically make one a Subject Matter Expert in driverless vehicle data. Relying on " usual " participants ignores the specialized nature of this specific project.
The PMI Standard for Project Management emphasizes that " Expert Judgment " should be sought from individuals or groups with specialized training or knowledge. By referring to the Stakeholder Register, the Project Manager ensures a structured and documented approach to engaging the correct expertise.

According to the Agile Practice Guide and the Standard for Portfolio Management, establishing a product roadmap in an adaptive environment is a strategic activity that requires alignment across different levels of the organization ' s hierarchy.
* Project Sponsor (A): The sponsor provides the vision and the funding for the project. In an adaptive environment, they are essential for ensuring the roadmap aligns with the business case and that the high- level milestones provide the expected return on investment (ROI).
* Portfolio Manager (B): The portfolio manager ensures that the product roadmap is aligned with the organization ' s strategic objectives and that it does not conflict with other initiatives within the portfolio. They provide the " big picture " context needed to prioritize the roadmap ' s themes.
* Program Manager (D): The program manager coordinates the dependencies between different projects or components that contribute to the product. They are instrumental in mapping out the timeline and ensuring that the roadmap is realistic given the shared resources and interdependencies across the program.
Analysis of other options:
* End user (C): While the end user is critical for providing feedback and helping refine User Stories or the Product Backlog, they are typically not involved in " establishing " the high-level strategic roadmap.
Their needs are represented by the Product Owner or Business Analyst.
* Internal inspector (E): This role is focused on compliance and quality control. While they may review the results of the work, they do not participate in the strategic planning or the drafting of the product roadmap.
Per PMI standards, the product roadmap serves as a high-level visual summary that maps out the vision and direction of the product offering over time. It requires the collaboration of the Sponsor, Portfolio Manager, and Program Manager to ensure financial, strategic, and operational alignment.

According to the PMBOKGuide, the Plan Resource Management process involves defining how to estimate, acquire, manage, and use team and physical resources. While the primary output is the Resource Management Plan, this process often results in Project Documents Updates.
* Stakeholder Register Updates: During Plan Resource Management, the project manager identifies the roles and responsibilities required for the project. In doing so, they may identify new stakeholders or realize that the requirements/expectations of existing stakeholders have changed based on the resource strategy. Therefore, the Stakeholder Register is frequently updated as an output of this process.
* Other Outputs:
* Resource Management Plan: The primary document describing how resources are categorized, allocated, and managed.
* Team Charter: A document that establishes the team values, agreements, and operating guidelines.
* Project Documents Updates: Including the Assumption Log and Risk Register.
Analysis of other options:
* A. Project charter: This is an output of the Develop Project Charter process (Initiating Phase) and actually serves as an input to Plan Resource Management.
* B. Risk register: The Risk Register is an output of Identify Risks. While it may be updated during resource planning, the Stakeholder Register is a more direct document update associated with identifying the people needed for the project.
* C. Scope baseline: This is an output of the Create WBS process within the Project Scope Management knowledge area.
Per PMI standards, Plan Resource Management ensures that the project team is structured correctly, and updating the Stakeholder Register is a necessary step to reflect the people involved in or impacted by that resource structure.