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

The stated scope uses vague terms like 'improve' and 'enhance' without defining what success looks like or what specific deliverables will be created. Effective project scope should be clear, specific, and measurable so the team knows what to deliver and stakeholders can determine when the project is complete.

**Why not A:** The methodology choice is not the primary concern with this scope definition. Whether the project uses agile, predictive, or hybrid approaches is a separate planning decision. The fundamental problem is that the scope lacks specific, measurable deliverables regardless of methodology.

**Why not C:** While the scope does describe desired outcomes (improve satisfaction, enhance experience), the issue is not that it focuses on benefits rather than features. The problem is that it lacks specific, measurable deliverables entirely. A good scope should define what the project will produce in concrete, verifiable terms.

**Why not D:** The project charter does not need to include technical architecture details. The charter provides a high-level scope description, and technical specifications are developed during planning. The concern is the vagueness of the scope, not the absence of technical detail.