CAPM Practice: Determine how project methodologies influence business analysis processes

The cone of uncertainty shows that early estimates can be significantly wrong — up to 4x in either direction. Predictive BAs must build flexibility into requirements rather than assuming false precision. Agile BAs use it to justify 'just-in-time' requirements refinement as real learning occurs.

**Why not A:** The cone of uncertainty does not describe the volume of requirements documentation growing over time. It is a project management concept that illustrates how the range of possible outcomes for estimates narrows as a project progresses and more information becomes available.

**Why not C:** Estimating requirements completeness is a separate analytical activity, not what the cone of uncertainty represents. The cone of uncertainty specifically addresses the variability in project estimates (cost, schedule, scope) at different stages, showing that early estimates carry the widest range of uncertainty.

**Why not D:** The cone of uncertainty has nothing to do with security vulnerabilities. It is an estimation and planning concept that visually depicts how uncertainty in project variables decreases progressively as the project moves through its lifecycle and decisions reduce the range of possible outcomes.