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

The clearest signal to avoid predictive is high uncertainty about the solution. When stakeholders don't fully know what they want, when the technology is unproven, or when the right approach requires discovery — applying a predictive methodology means committing to a plan before the key information is known, creating high risk of building the wrong thing.

**Why not B:** Having a fixed deadline does not preclude a predictive approach — in fact, fixed deadlines are common in predictive projects. Predictive methodology can accommodate fixed deadlines through detailed planning and schedule management. A deadline constraint alone does not indicate whether predictive or adaptive is appropriate.

**Why not C:** Large, geographically distributed teams can successfully use either predictive or adaptive approaches. Team size and distribution are logistical considerations that can be addressed within either methodology through appropriate communication and coordination tools.

**Why not D:** Having a defined budget is compatible with both predictive and adaptive approaches. Predictive projects plan costs upfront against a budget baseline, while adaptive projects can manage budgets through sprint-level cost tracking. A defined budget does not determine methodology choice.