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

The key test for predictive suitability is whether requirements can be sufficiently defined upfront and will remain stable during execution. If stakeholders can articulate what they want clearly, if the domain is understood, and if major changes are not expected, predictive planning will be effective. Budget size, team size, and organizational history are secondary considerations.

**Why not A:** Whether the organization has used predictive approaches before is relevant to organizational capability and experience, but it does not directly address whether the project's requirements are stable enough for a predictive approach. Familiarity with the methodology does not determine requirement stability.

**Why not C:** Project budget size does not determine whether requirements are stable. Large and small projects alike can have either stable or volatile requirements. The suitability of a predictive approach depends on requirement clarity and expected change, not on financial scale.

**Why not D:** The number of team members is a resource consideration, not a requirement stability indicator. Team size affects execution capacity but does not determine whether requirements can be defined upfront and will remain stable during the project.