CAPM Practice: Determine how project methodologies influence business analysis processes

Retrospectives provide a structured opportunity to improve requirements quality. If stories were poorly defined, acceptance criteria unclear, or stakeholder feedback insufficient, the team can identify and address these BA-related process issues in the retrospective.

**Why not A:** Retrospectives are not purely technical events. They examine all aspects of the team's work, including requirements quality, stakeholder communication, and BA practices. The team reflects on what went well and what can improve across all dimensions of their collaborative process.

**Why not B:** Retrospectives address far more than team relationship issues. They examine work quality, process effectiveness, tool adequacy, and communication patterns. Requirements-related improvements such as better story definitions and clearer acceptance criteria are frequently discussed topics.

**Why not D:** BAs should participate in sprint retrospectives because their work directly affects sprint outcomes. If stories were unclear or acceptance criteria ambiguous, the retrospective is where the team identifies these patterns and agrees on improvements. Excluding BAs removes a key perspective from the improvement discussion.