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

An adaptive (agile) approach is best suited when requirements are expected to evolve and change frequently. This approach embraces change through iterative cycles and continuous feedback, allowing the team to adjust based on user input.

**Why not A:** A hybrid approach combines predictive and adaptive elements, but this project's primary characteristic is continuously evolving requirements based on user feedback after each iteration. The situation does not describe any components that need predictive planning, making a purely adaptive approach the better fit.

**Why not C:** A predictive approach with a change control board is designed for stable requirements with formal change management. When requirements are expected to change frequently based on ongoing user feedback, the overhead of formal change requests becomes a bottleneck rather than a benefit.

**Why not D:** A predictive approach with detailed upfront planning assumes requirements are well-known and stable. The scenario explicitly states that requirements keep changing based on user feedback, which directly contradicts the predictive approach's assumption of stable, fully defined scope.