According to the PMBOK® Guide (6th Edition), the Collect Requirements process is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives. Because this process occurs early in the planning phase, it relies on high-level foundational documents to provide context.
The specific inputs for the Collect Requirements process include:
Project Charter: Used to provide the high-level project description and high-level requirements that will be used to derive detailed requirements.
Business Documents: Specifically the Business Case, which describes the required, desired, and optional criteria for meeting business needs.
Project Management Plan: (Specifically the Scope, Requirements, and Stakeholder Engagement management plans).
Project Documents: (Specifically the Stakeholder Register, Lessons Learned Register, and Assumption Log).
Agreements: If the project is under a contract.
EEFs and OPAs.
Analysis of Distractors:
A (Requirements documentation): This is an output of the Collect Requirements process, not an input. You cannot use the finished documentation to start the process of collecting them.
C (Stakeholder requirements): This is a category of requirements that are identified during the process. The input used to find these stakeholders is the Stakeholder Register.
D (Requirements traceability matrix): Like requirements documentation, the matrix is a primary output of this process. It is used later in the project to track requirements, but it does not exist until the Collect Requirements process is performed.
Key Concept: The Project Charter provides the " why " and the high-level " what, " while the Business Documents provide the economic and strategic justification. Together, they form the boundary within which detailed requirements are gathered.