CAPM Practice: Determine how project methodologies influence business analysis processes

Agile doesn't eliminate requirements documentation — it distributes it differently. The backlog (user stories, acceptance criteria) is the primary requirements repository, supplemented by process models, data models, and architectural documents as needed. The BRD is replaced by a collection of lighter artifacts.

**Why not A:** Agile projects do not use the same BRD with minor format changes. The fundamental approach to requirements documentation differs in agile, favoring a collection of lighter-weight artifacts over a single comprehensive document. The shift is philosophical, not merely cosmetic.

**Why not B:** Agile projects do document requirements, just differently. The product backlog, user stories, acceptance criteria, and supporting artifacts all serve as requirements documentation. The misconception that agile means no documentation contradicts the Agile Manifesto, which values working software over comprehensive documentation, not over all documentation.

**Why not C:** The sprint backlog alone does not replace the BRD. The sprint backlog contains only the work items selected for the current sprint, while the product backlog, product vision, release roadmap, and other complementary artifacts collectively provide the broader requirements context that a BRD would cover.