CAPM Practice: Determine how project methodologies influence business analysis processes

The 'requirements freeze' in predictive projects occurs when knowledge is at its lowest — before any development has occurred. Real learning about user needs, technical constraints, and business context emerges through delivery, often invalidating upfront requirements that can't easily be changed.

**Why not A:** Predictive methodologies are typically criticized for the opposite reason — they invest heavily in thorough upfront requirements gathering, not for being too fast. Speed of requirements development is not the core risk; the problem is that extensive early requirements are captured before stakeholders and developers have built shared understanding.

**Why not C:** Predictive methodologies do include formal stakeholder reviews — they typically require sign-offs and walkthroughs before baselining. The fundamental risk is not the absence of review, but that requirements are frozen too early, when business knowledge and technical understanding are still immature.

**Why not D:** Predictive projects are often faulted for producing too many requirements rather than too few. The risk is not volume but timing and rigidity — comprehensive requirements documented before design and development makes them costly to change when reality diverges from the initial plan.