PGMP · Question #33
You are the project manager for your organization and are working with the project stakeholders and the business analyst to define all of the deliverables the project is to create. The stakeholders wo
The correct answer is B. Project scope statement. The project scope statement defines exactly what the project will and will not deliver - the boundaries, deliverables, acceptance criteria, constraints, and assumptions. The project manager specifically needs a document that locks down what must be delivered (as opposed to keepin
Question
You are the project manager for your organization and are working with the project stakeholders and the business analyst to define all of the deliverables the project is to create. The stakeholders would like the option of adding more deliverables later in the project and keeping the requirements somewhat open for changes. You explain to the business analyst that you need a set of requirements that define exactly what needs to be delivered for the project. What document are you trying to create in this early stage of the project?
Options
- ARequirements technical documentation
- BProject scope statement
- CProject charter
- DDetail design document
How the community answered
(16 responses)- A6% (1)
- B94% (15)
Explanation
The project scope statement defines exactly what the project will and will not deliver - the boundaries, deliverables, acceptance criteria, constraints, and assumptions. The project manager specifically needs a document that locks down what must be delivered (as opposed to keeping requirements open), which is the project scope statement. A requirements technical document (A) describes technical specifications, not the full scope boundary. The project charter (C) is a higher-level authorization document created earlier that does not define detailed deliverables. A detail design document (D) is a technical artifact produced later in the project. The scenario emphasizes the need for a definitive list of deliverables to push back against open-ended stakeholder changes, which is exactly the purpose of the project scope statement.
Topics
Community Discussion
No community discussion yet for this question.