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

In predictive projects, BAs produce a Business Requirements Document (BRD) or similar artifacts. In agile projects, requirements are captured as user stories in the product backlog. The format varies, but the BA ensures requirements are clearly documented.

**Why not A:** The work breakdown structure (WBS) decomposes project deliverables into work packages for scheduling and resource planning. It is a project management artifact, not a requirements communication document produced by the BA.

**Why not B:** The project charter authorizes the project and defines high-level objectives, scope, and constraints. It is created before detailed requirements work begins and is not the artifact BAs use to capture and communicate detailed requirements to the team.

**Why not C:** The resource management plan describes how project resources (people, equipment, materials) will be acquired, managed, and released. It addresses staffing and resource allocation, not requirements capture and communication.