CAPM Practice: Determine how project methodologies influence business analysis processes

BAs contribute to risk management across all methodologies: identifying requirements risks (ambiguity leads to wrong features), stakeholder risks (disengaged stakeholders lead to missed needs), and business risks (changing market conditions). The timing of this work adapts to the methodology.

**Why not A:** Business analysts do not focus exclusively on technical risks. BAs contribute to identifying a wide range of risks including requirements-related risks, stakeholder risks, process risks, and solution adoption risks. Their broad organizational perspective allows them to spot business and operational risks that technically focused team members might overlook.

**Why not B:** Risk management is not exclusively the project manager's responsibility. While the PM typically owns the overall risk management plan, risk identification and assessment is a collaborative effort. The BA brings unique insight into requirements gaps, stakeholder conflicts, and solution feasibility that are essential inputs to effective risk management.

**Why not D:** Business analysts participate in risk management activities across all methodologies, not just specific ones. Whether the project follows predictive, adaptive, or hybrid approaches, the BA contributes to identifying risks related to requirements completeness, stakeholder alignment, and solution viability. Their involvement is methodology-agnostic and consistently valuable.