CAPM Practice: Determine how project methodologies influence business analysis processes

Each methodology context emphasizes different BA tools: agile toolkits lean toward collaborative, lightweight artifacts (stories, BDD scenarios, wireframes); traditional toolkits include comprehensive documentation artifacts (BRDs, functional specs, data dictionaries). Effective BAs draw from both as appropriate.

**Why not A:** Both toolkits do not contain identical techniques with different labels. While some techniques overlap, the emphasis and artifact types differ significantly. Agile BAs prioritize collaborative, lightweight artifacts, while traditional BAs emphasize comprehensive, formal documentation. The distinction is substantive, not just terminological.

**Why not B:** Traditional BAs do not have more tools simply because agile eliminates documentation. Agile BAs use different tools, not fewer. Story mapping, BDD scenarios, collaborative workshops, and rapid prototyping are agile-specific tools that replace rather than simply remove traditional documentation-heavy techniques.

**Why not D:** The distinction between agile and traditional BA toolkits is not about digital versus paper-based tools. Both methodologies use a mix of digital and physical tools. The real difference lies in artifact weight, collaboration intensity, and the degree to which documentation is considered sufficient versus comprehensive.