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

This digital transformation initiative has multiple uncertainty indicators (emerging AI, behavioral change, uncertain integration) that contradict predictive methodology's core assumption of stable, knowable requirements. Even with organizational expertise in predictive methods, forcing this project into a predictive framework risks building to incorrect specifications. An adaptive or hybrid approach would allow discovery, iteration, and course-correction as knowledge develops.

**Why not B:** Letting the IT department decide alone ignores the strategic methodology decision that should involve project management leadership. Methodology selection requires evaluating project characteristics, not just deferring to the executing department's preference.

**Why not C:** Using predictive because the company has expertise in it ignores the project's characteristics. Methodology should match the project, not the organization's comfort zone. Forcing a high-uncertainty initiative into a familiar but unsuitable framework increases the risk of failure.

**Why not D:** Adding extra risk planning to a predictive approach does not address the fundamental mismatch. The uncertainty in this initiative is not a risk to be managed within a plan — it is a characteristic that requires iterative discovery. Predictive methodology cannot compensate for unknown requirements through better risk management alone.