Which of the following are outputs of define scope process in project scope management

According to the PMBOK® Guide, the Define Scope process is the process of developing a detailed description of the project and product. It is critical because it describes the product, service, or result boundaries and acceptance criteria.

Project Scope Statement (Choice C): This is the primary output of the Define Scope process. It includes the product scope description, deliverables, acceptance criteria, and project exclusions.

Project Documents Updates (Choice C): This is the second standard output. During this process, documents such as the Assumption Log, Requirements Documentation, Requirements Traceability Matrix, and Stakeholder Register may be updated as more detail is uncovered about the scope.

Requirements documentation and RTM (Choice A): These are the primary outputs of the Collect Requirements process, which precedes Define Scope.

Scope Management Plan and Requirements Management Plan (Choice B): These are outputs of the Plan Scope Management process.

Scope Baseline (Choice D): The Scope Baseline is an output of the Create WBS process. It is composed of the approved version of the Project Scope Statement, the WBS, and the WBS Dictionary.

The transition from the Collect Requirements process to Define Scope is where the project manager selects the final requirements from the requirements documentation to be included in the project, which are then documented in the Project Scope Statement.