CAPM Practice: Demonstrate an understanding of business analysis (BA) roles and responsibilities

Agile analysis is continuous, collaborative, and lightweight. BAs work within sprints — refining backlog items for upcoming iterations, writing acceptance criteria, facilitating story elaboration — rather than producing comprehensive specifications before any development begins.

**Why not A:** Agile analysis is performed by business analysts (or team members filling the BA role), not exclusively by agile coaches. The BA role remains essential in agile; the approach to analysis changes, but the analyst role is not replaced by coaching.

**Why not B:** Agile analysis covers all types of requirements — business, functional, and non-functional — not just technical requirements for software. It addresses the full range of stakeholder needs using iterative, collaborative methods within sprint cycles.

**Why not C:** Agile analysis is not simply a faster version of traditional analysis with the same outputs. It fundamentally changes the approach — using lightweight artifacts like user stories and acceptance criteria instead of comprehensive specification documents, and performing analysis just-in-time rather than all upfront.