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

The greatest risk of using predictive methodology for unclear requirements is 'building the wrong thing.' When requirements are unclear but locked in early, the team may execute perfectly against a flawed plan. Without mechanisms for discovery and adaptation, the completed product may not meet actual user needs — resulting in waste even with successful project execution.

**Why not A:** Difficulty assigning roles and responsibilities is not a significant risk specific to using predictive with unclear requirements. Role assignment challenges can occur in any methodology and are addressed through organizational planning, not methodology selection.

**Why not B:** Predictive approaches do not use iterative planning sessions — that is an adaptive characteristic. Spending too much time in iterative planning would not be a risk of predictive methodology since predictive projects plan comprehensively upfront rather than iteratively.

**Why not C:** Excessive stakeholder engagement is not a characteristic risk of predictive approaches. In fact, predictive projects typically have less continuous stakeholder engagement than adaptive projects, which rely on frequent feedback loops. The risk is too little engagement, not too much.