During initiation of the Hoover Dam redevelopment project, the scope statement is high level and lacks many detailed descriptions. Your team wants to postpone work until more detail is available. As the project manager, what should you recommend?

Introduction / Context:
Early in a project, especially during initiation, scope statements are often high level and may not include all of the detailed requirements that will ultimately be needed. PMI introduces the concept of progressive elaboration, which means that project characteristics are elaborated and refined over time as more information becomes available. Understanding this concept helps project managers avoid unnecessary delays while still managing uncertainty responsibly.

Given Data / Assumptions:

• The Hoover Dam redevelopment project is in the initiation phase.
• A high level scope statement exists but lacks detailed descriptions and lower level requirements.
• The team is uncomfortable and wants to postpone work until more detail is provided.
• The question asks what a professional project manager should recommend in this situation.

Concept / Approach:
During initiation, it is normal for scope to be defined at a high level. The project manager should confirm the high level objectives and constraints with stakeholders and then plan to elaborate details during the planning phase and as the project progresses. Progressive elaboration and rolling wave planning are used to plan near term work in detail while leaving distant work at a higher level until more information is known. Completely stopping the project until every detail is defined would delay value and is not aligned with PMI practices, as long as there is enough clarity to proceed to planning and further definition.

Step-by-Step Solution:
Step 1: Recognize that projects seldom start with a fully detailed scope; initiation typically produces a high level scope statement. Step 2: Recall the concept of progressive elaboration, where details are refined over time as the project is planned and executed. Step 3: Consider that the correct response is not to postpone the entire project but to confirm high level scope and then plan to elaborate details later. Step 4: Review answer choices and identify the one that explicitly references moving forward while acknowledging that more detail will emerge as characteristics are progressively elaborated. Step 5: Select option C, which captures this balanced approach consistent with PMI guidance.

Verification / Alternative check:
PMI's discussions of scope planning and progressive elaboration state that initial project documents such as the project charter and early scope descriptions are high level. As the project moves into detailed planning, these documents are expanded into more precise scope statements, requirements documents, and work breakdown structures. This staged refinement process confirms that the team should not expect complete detail at initiation and supports proceeding with verification of high level scope first, rather than delaying the entire project.

Why Other Options Are Wrong:
Option A overemphasizes risk and suggests delay, though there is no indication that the project lacks enough clarity to proceed to planning. Option B insists on complete detailed agreement before moving forward, which is unrealistic and contrary to progressive elaboration. Option D suggests revisiting selection criteria or canceling the project without evidence that it is misaligned with strategy. Option E is inappropriate because unilaterally rewriting the scope without stakeholder input undermines stakeholder engagement and governance. Only option C reflects PMI's recommended approach to high level scope at initiation.

Common Pitfalls:
A common pitfall is expecting perfect information before starting a project, leading to analysis paralysis and missed opportunities. Another is ignoring the lack of detail altogether, which can cause confusion later if expectations are not clarified. Progressive elaboration provides a middle path: start with high level agreement, then refine details as planning and execution proceed. Understanding this concept allows project managers to move forward responsibly, especially on complex projects like infrastructure redevelopment.

Final Answer:
The best recommendation is to move forward and verify the high level scope, explaining that additional details will be developed progressively as more information becomes available.