CAPM Practice: Determine how project methodologies influence business analysis processes

Methodology shapes the BA-PM relationship. Predictive projects often sequence BA work (requirements) before PM delivery planning. Adaptive projects require continuous BA-PM collaboration — the PM plans the sprint while the BA refines the backlog for the next sprint simultaneously.

**Why not A:** Claiming BA and PM roles are always completely separate ignores how methodology fundamentally shapes their interaction. In adaptive projects, BA and PM activities overlap significantly — they collaborate daily on backlog management, sprint planning, and stakeholder communication in ways that blur traditional role boundaries.

**Why not B:** The BA does not universally report to the PM across all methodologies. In agile frameworks like Scrum, there is no formal reporting relationship between these roles. The BA may work alongside the product owner or function as a team member with a peer relationship to the PM, depending on the organizational structure.

**Why not D:** In agile projects, the BA does not replace the project manager. While some agile frameworks de-emphasize traditional PM responsibilities, the roles remain distinct. A Scrum Master or agile PM handles delivery facilitation and impediment removal, while the BA focuses on requirements elicitation, analysis, and stakeholder collaboration.