CAPM Practice: Determine how project methodologies influence business analysis processes

Sprint reviews perform a key BA function: validating the solution against business needs with real stakeholder feedback. BAs use sprint review outcomes to refine acceptance criteria, adjust backlog priorities, and update requirements understanding — continuous validation rather than end-of-project acceptance testing.

**Why not B:** Sprint reviews are not internal team events. They are specifically designed for stakeholder attendance and feedback. Stakeholders, product owners, and BAs participate to review the increment, provide input, and influence future backlog priorities based on what they observe.

**Why not C:** The sprint review is not a technical meeting for code quality assessment. That describes a code review or technical review. Sprint reviews focus on demonstrating working software to stakeholders and gathering business-oriented feedback on whether the delivered increment meets needs and expectations.

**Why not D:** The sprint review is not where the BA presents a complete requirements document for approval. In agile projects, requirements are expressed as backlog items refined over time, not as comprehensive documents. The sprint review demonstrates working software, and feedback from that demonstration informs future requirements.