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

When requirements are evolving and stakeholder needs are changing, an adaptive (iterative/agile) approach is more suitable. Adaptive approaches embrace change and allow teams to adjust direction based on feedback and learning, which fits this scenario where technology and customer needs are shifting.

**Why not A:** Running both approaches simultaneously creates unnecessary complexity and overhead. It does not solve the core problem of evolving requirements. A clear transition to adaptive methodology would provide the team with a consistent framework for responding to the changing technology landscape.

**Why not B:** Pausing the project until all requirements are fully defined contradicts the reality that requirements are still evolving. In a rapidly shifting technology landscape, waiting for complete requirements could mean waiting indefinitely while competitors move ahead and customer needs continue to change.

**Why not D:** Continuing with the predictive approach when the original requirements are now less valuable due to a major technology shift would mean building to outdated specifications. The detailed plans created months ago are based on assumptions that no longer hold, making them an unreliable guide for the remaining work.