According to the PMBOK Guide, 7th edition, section 5.3.1, “The project scope statement is a component of the project management plan that describes, in detail, the project’s deliverables and the work required to create those deliverables. It provides a common understanding of the project scope among project stakeholders and describes the project’s major deliverables, assumptions, and constraints.” Therefore, the project manager should meet with management to explain the potential problems with running a project without a project scope statement, such as scope creep, misalignment of expectations, poor quality, increased risks, and wasted resources. Escalating the issue to the project sponsor and adding it to the risk register (option A) may be done after meeting with management, but not before. Refusing to work on the project because management is not following standard project management practices (option B) is unprofessional and may damage the relationship with the management and the project stakeholders. Starting the project with inputs from the project charter to save time (option D) may not be feasible or effective, as the project charter is a high-level document that does not provide enough details to define and control the project scope. References:

PMBOK Guide, 7th edition, section 5.3.1

PMI-PBA Exam Practice Test and Study Guide, 2nd edition, page 182, question 18