CAPM Practice: Determine how project methodologies influence business analysis processes

The appropriate BA practice intensity scales with project complexity and team size. Small, simple projects don't need the same governance overhead as large programs. The BA should calibrate formality, documentation, and governance to the project's actual complexity and risk level.

**Why not A:** This incorrectly pairs complexity with methodology choice. Complex projects may actually benefit from predictive BA when requirements are well-understood, and simple projects may use adaptive BA when requirements are uncertain. Complexity alone does not dictate methodology.

**Why not B:** Team size does not automatically determine methodology. Large teams can use agile frameworks like SAFe, and small teams sometimes use predictive approaches for well-defined projects. The relationship between team size and methodology is not a simple binary mapping.

**Why not D:** BA practices must scale with project complexity and team size. A five-person team building a simple internal tool needs different governance and documentation than a 200-person program implementing an enterprise system. One-size-fits-all BA practices waste effort on small projects and under-serve large ones.