Project Scope Management Plan

Correct Answer: Evaluate the impact on the project scope, schedule, and cost.

The best answer is 'Evaluate the impact on the project scope, schedule, and cost.'. A project manager's first step when a client requests additional features should be to assess how these changes would impact the overall project. Balancing the scope, schedule, and cost of a project is key to successful project management, and any changes could potentially upset this balance. Once the impact is understood, the project manager can then make an informed decision about whether to accept the additional features, negotiate changes, or reject the request. The other options are not advisable. Accepting the request immediately may lead to overpromising and underdelivering, causing delays or cost overruns. Similarly, directing the team to implement changes without understanding the implications can introduce risk and lead to project failure. Rejecting the request without considering its value to the client and the project may harm the relationship with the client and potentially lose beneficial enhancements to the project.

Correct Answer: Scope statement

The best document to review when the project team complains about unclear project deliverables and scope creep is the 'Scope statement'. The scope statement document provides a detailed description of the project's deliverables and also defines what is in and out of the project's scope, which helps in avoiding scope creep. On the other hand, 'Project charter' is a high-level document that provides a broad overview of the project but does not detail the project deliverables. A 'Risk management plan' pertains to potential risks and their management strategies, and a 'Quality management plan' pertains to the standards of quality to be maintained in the project - in this context neither of these would address the specific issue of ill-defined deliverables and scope creep.

Correct Answer: Scope statement, WBS, and WBS Dictionary.

The scope baseline of a project includes the project scope statement, the Work Breakdown Structure (WBS), and the WBS dictionary. The scope statement is a detailed description of the project's deliverables and the work required to create those deliverables. The WBS organizes the team's work into manageable sections, while the WBS dictionary provides a detailed description of each component in the WBS. The other options are incorrect because they include elements like milestones, assumptions, and cost estimates, or stakeholder lists and charts, or resource lists and change logs which while important for the project management, are not specifically part of the scope baseline.