CAPM Practice: Determine how project methodologies influence business analysis processes

Requirements volatility is a key input to methodology selection. When customer needs are evolving rapidly, markets are uncertain, or technology is novel, high volatility makes adaptive approaches more suitable. Stable, well-understood requirements with low change rates may justify predictive documentation.

**Why not A:** Requirements volatility refers to the frequency and magnitude of changes to requirements themselves, not to team member turnover. While team turnover can affect institutional knowledge about requirements, it is a staffing concern — distinct from the concept of how rapidly the requirements evolve or shift during a project.

**Why not B:** Requirements volatility is a business analysis concept describing how much requirements change over time, not a technical metric for software tools. It has nothing to do with database stability or the performance of requirements management platforms. This answer confuses a conceptual measure with a technical infrastructure metric.

**Why not C:** Different methodologies handle requirements volatility in fundamentally different ways. Predictive methodologies assume stable requirements and invest in upfront documentation, while adaptive methodologies embrace change through iterative delivery. Claiming all methodologies respond identically ignores the core philosophical differences that distinguish these approaches.