CAPM Practice: Determine how project methodologies influence business analysis processes

Methodology fundamentally shapes when and how BA work occurs. Waterfall-style projects concentrate requirements gathering in early phases; agile projects spread BA activities across iterations with continuous refinement, sprint review feedback, and evolving acceptance criteria.

**Why not A:** BA activities do not occur only at the end of a project. In both predictive and adaptive methodologies, requirements gathering and analysis happen well before the final validation phase. Limiting BA work to the end would mean building without defined requirements.

**Why not C:** BA activities do not always occur only at the beginning regardless of methodology. While predictive projects front-load analysis, adaptive projects distribute BA work continuously across iterations. The timing of BA activities is fundamentally shaped by the chosen methodology.

**Why not D:** Project methodology has a significant effect on the timing of BA activities. Predictive projects concentrate requirements gathering in early phases, while adaptive projects spread analysis across iterations with ongoing refinement. Ignoring this relationship leads to misaligned expectations about when requirements will be ready.