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

Solution scope describes what the product does (features, capabilities). Project scope describes all work required to deliver the project — including analysis, design, testing, training, and rollout. BAs primarily define solution scope.

**Why not B:** Solution scope and project scope are distinct concepts that should not be used interchangeably. Conflating them leads to confusion about what the product must do versus what work the project team must perform. The BABOK and PMBOK both recognize these as separate concepts with different owners and management approaches.

**Why not C:** This reverses the actual relationship. Solution scope defines product features and capabilities, not budget. Project scope encompasses all work required to deliver the solution, which inherently includes financial planning and resource allocation. Budget considerations are part of project scope, not solution scope.

**Why not D:** While project scope is broader than solution scope, characterizing solution scope as limited to software features is inaccurate. Solution scope encompasses all features and functions of the delivered product, which may include hardware, processes, training, organizational changes, and other non-software components depending on the nature of the solution.