CAPM Practice: Determine how project methodologies influence business analysis processes

Scrum distributes traditional BA functions — the Product Owner owns the backlog; the team collaboratively refines stories. A BA may serve as PO, support the PO, or perform analysis work iteratively within sprints rather than front-loading a requirements phase.

**Why not B:** Claiming BAs are unnecessary in Scrum oversimplifies the relationship between roles. While the product owner handles product decisions, BAs bring specialized skills in requirements elicitation, stakeholder analysis, and process modeling that complement the product owner role. Many Scrum teams benefit from BA expertise, especially in complex domains.

**Why not C:** In Scrum, requirements work is continuous, not confined to an initial planning phase. BAs participate throughout the project in backlog refinement, sprint planning, acceptance criteria writing, and stakeholder collaboration. Limiting BA involvement to upfront planning contradicts the iterative nature of Scrum.

**Why not D:** The BA role is distinctly different between Scrum and waterfall. In waterfall, BAs typically produce comprehensive upfront requirements documents before development begins. In Scrum, BAs work iteratively, collaborating closely with the team throughout sprints and continuously refining requirements as understanding evolves.