CAPM Practice: Determine how project methodologies influence business analysis processes

SAFe introduces structured planning at multiple levels. BAs may work at: portfolio level (analyzing epics, business outcomes), program level (decomposing features, PI planning support), and team level (story refinement, acceptance criteria). Requirements hierarchy matches the planning hierarchy.

**Why not A:** SAFe involves multiple teams with different needs, so one BA cannot serve all teams identically. BAs must adapt their work to the appropriate level — portfolio epics require different analysis than team-level user stories — and may specialize at different levels of the framework.

**Why not C:** SAFe is an agile scaling framework, not a waterfall approach. It uses agile practices like user stories, acceptance criteria, and iterative delivery at the team level, while adding structured planning ceremonies like PI Planning at the program level.

**Why not D:** SAFe does not eliminate the need for BA work. While teams are self-organizing in their execution, the complexity of multi-team coordination, feature decomposition, and cross-team dependency management actually increases the need for BA skills at portfolio, program, and team levels.