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

A hybrid approach is best because the project has fixed constraints (budget, timeline, infrastructure) that benefit from predictive planning, while the user interface has uncertain requirements that benefit from adaptive iterations. This balances the need for structure with flexibility where it matters most.

**Why not A:** Using a purely adaptive approach ignores the fixed budget and firm deadline constraints. While the user interface requirements are uncertain, the infrastructure and system integration components have stable requirements that benefit from predictive planning. A hybrid approach addresses both needs.

**Why not B:** Starting with predictive and switching to adaptive mid-project creates disruption and lacks planning discipline. A hybrid approach is planned from the start, deliberately assigning predictive methods to stable components and adaptive methods to uncertain ones, rather than reacting to changes after the fact.

**Why not D:** Using a purely predictive approach ignores the executive sponsor's warning that customer feedback will require significant UI changes. Predictive approaches assume stable requirements, and rigid upfront planning for the user interface would result in costly rework when feedback-driven changes inevitably arise.