CAPM Practice: Determine how to gather requirements

Gap analysis systematically identifies the difference between where the organization is and where it needs to be. Each identified gap represents a requirement — the solution must bridge the gap. This ensures requirements are grounded in real business need rather than feature wishes.

**Why not A:** Gap analysis is not about evaluating individual team member performance deficiencies. While "gap" might suggest performance shortfalls, in business analysis gap analysis specifically examines the difference between the current state of a business process or capability and the desired future state to identify what changes are needed.

**Why not C:** Gap analysis does not focus on finding missing or incomplete documentation. While documentation gaps can be a concern in any project, gap analysis as a BA technique is a structured comparison of current-state capabilities against future-state requirements to determine what must change to achieve business objectives.

**Why not D:** Gap analysis is not a technique for identifying budget shortfalls. Financial analysis and budget variance tracking are separate disciplines. Gap analysis in business analysis examines the functional, process, or capability differences between where an organization is today and where it needs to be.