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

An adaptive approach is best suited for projects with unclear or evolving requirements. It allows for iterative development, frequent feedback, and flexibility to incorporate changes as understanding improves.

**Why not A:** A predictive approach with change control board approval is designed for projects with well-understood, stable requirements. When requirements are unclear and likely to evolve, a rigid approval process for every change would slow progress and conflict with the need for flexibility.

**Why not B:** A hybrid approach using only the planning phase adaptively is too limited. If requirements are expected to evolve throughout the project, the entire development process should be adaptive, not just the planning phase.

**Why not C:** A predictive approach with detailed upfront planning requires well-defined requirements from the start. Since the customer requirements are unclear and likely to change, extensive upfront planning would be based on incomplete information and would need constant rework.