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

Assumptions analysis surfaces hidden beliefs that, if false, could jeopardize the project. BAs challenge assumptions (e.g., 'Users will adopt the new system easily') to prevent projects from failing on unstated, unvalidated beliefs.

**Why not B:** Assumptions analysis in business analysis is broader than just financial or budget assumptions. It encompasses all beliefs taken as true about the project environment, stakeholders, technology, and business context. Financial assumption analysis is only one narrow subset of the overall practice.

**Why not C:** While stakeholder assumptions about their processes may surface during assumptions analysis, this answer is too narrow. Assumptions analysis examines beliefs across all project dimensions — business, technical, organizational, and environmental — not just stakeholder self-assessments of their internal processes.

**Why not D:** Testing technical assumptions made by developers is a development activity, not the BA practice of assumptions analysis. The BA technique focuses on identifying and documenting assumptions early to assess their validity and associated risks, rather than testing implementation-level technical choices during coding.