CAPM Practice: Explain when it is appropriate to use a predictive, plan-based approach

Project X (uncertain market fit, novel product, inexperienced team) has high uncertainty and unknown requirements — classic indicators for adaptive. Discovery and iteration are needed. Project Y (documented procedures, experienced team, fifth repetition, regulatory requirements) has stable, known requirements and compliance demands — classic indicators for predictive. Methodology selection should match the uncertainty profile of each project.

**Why not A:** Assigning Project X to predictive and Project Y to adaptive reverses the correct methodology alignment. Project X's high uncertainty and novel product development call for adaptive, while Project Y's documented procedures and regulatory requirements call for predictive.

**Why not B:** Using adaptive for both projects ignores Project Y's characteristics. Project Y has documented procedures, an experienced team, five prior repetitions, and regulatory compliance requirements — all strong indicators for predictive methodology. Not every project benefits from adaptive approaches.

**Why not D:** Using predictive for both projects ignores Project X's high uncertainty and novel nature. A fixed timeline alone does not justify predictive methodology. Project X's uncertain market fit and inexperienced team with the product type require the discovery and flexibility that adaptive approaches provide.