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

When a planned approach proves infeasible during execution, the project manager must document the situation, identify and evaluate alternatives, assess the impact of each alternative on scope/schedule/cost, and submit a change request for formal approval. The plan cannot simply be deviated from without going through change control, even when a deviation is technically necessary.

**Why not A:** Switching to an adaptive approach mid-project for one component is an overreaction to a feasibility issue. The predictive framework has built-in mechanisms (change control) to handle plan modifications. A single infeasible technical approach does not necessitate abandoning the project's methodology.

**Why not C:** Continuing with a documented approach that has been proven infeasible would waste time and resources. While the approach was formally approved, reality has changed. The appropriate response is to formally update the plan through change control, not to persist with a known-infeasible approach.

**Why not D:** Asking the team to find a workaround without updating the official plan creates a disconnect between actual work and documented plans. This bypasses change control and undermines project governance. All significant deviations from the plan must go through formal change management.