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

Historical precedent is a strong indicator for predictive suitability. When similar projects have been done before, requirements are understood, the technology is known, and processes are established — minimizing uncertainty and making comprehensive upfront planning feasible and valuable.

**Why not A:** Completely new technology with no prior examples creates high uncertainty, which is the opposite of what predictive methodology handles well. Unknown technology requires iterative exploration and discovery, favoring adaptive approaches over comprehensive upfront planning.

**Why not B:** A highly volatile market with changing customer needs means requirements will shift during the project. Predictive methodology assumes stable requirements; constant change would undermine the front-loaded planning approach and require frequent baseline revisions.

**Why not C:** Extensive stakeholder collaboration to discover requirements indicates that requirements are not well-defined upfront. If requirements must be discovered through collaboration, an adaptive approach that supports iterative discovery is more appropriate than predictive upfront specification.