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

All three characteristics (undocumented legacy functionality, evolving requirements, new technology) are uncertainty indicators that favor adaptive approaches. Requirements cannot be fully defined upfront (legacy system unknowns), change is expected (evolving requirements), and technical risk is high (new technology). Applying predictive methodology in this context risks building to incorrect requirements with high change costs.

**Why not A:** IT projects do not always need predictive approaches with formal change control. Many IT projects, especially those with evolving requirements, benefit from adaptive approaches that embrace change rather than controlling it through formal processes.

**Why not B:** Project size and budget alone do not determine the appropriate approach. Large projects with high uncertainty and evolving requirements may benefit more from adaptive or hybrid approaches than from predictive ones. The nature of the uncertainty matters more than the budget.

**Why not C:** Having a defined start and end date is a characteristic of all projects, not a reason to choose predictive methodology. Both predictive and adaptive projects have defined timelines — the methodology choice depends on requirement stability and uncertainty levels.