CAPM Practice: Demonstrate an understanding of the various project life cycles and processes

The scope lacks specificity needed for successful project execution. Measurable deliverables and clear acceptance criteria are essential to prevent scope creep and ensure stakeholder alignment. Neha should advocate for proper scope definition before work begins, which demonstrates professional responsibility.

**Why not A:** Beginning work immediately with vague scope like "improve customer satisfaction" and "reduce support costs by 30%" without specific deliverables or acceptance criteria virtually guarantees scope creep, stakeholder misalignment, and difficulty measuring success. Clarification should come before execution.

**Why not C:** Escalating to the PMO to reject the charter entirely is an overreaction. The charter has valid business objectives — it just needs more specific deliverables and acceptance criteria. The appropriate action is to work with the sponsor to add the missing specificity, not to reject the entire project.

**Why not D:** Proceeding as directed simply because the sponsor approved the charter ignores the PM's professional responsibility to advocate for proper scope definition. An experienced PM should explain the risks of vague scope and recommend clarification before starting work.