A business analyst is working on a project to implement a new inventory management system. The project charter has been approved, and the project manager has asked the analyst to begin requirements elicitation. The analyst notices that the business case did not include a clear problem statement or measurable objectives. Several stakeholders are uncertain about the project's purpose and expected outcomes. The project sponsor is eager to move forward. As the business analyst, what should you do first?
A solid business case provides direction and success criteria for all subsequent activities.
Why this answer
The business case provides the foundational justification for the project, including the problem statement and measurable objectives. Without these, requirements elicitation lacks clear direction, leading to scope creep and misaligned outcomes. The business analyst must first refine the business case with the sponsor and key stakeholders to ensure a shared understanding of the project's purpose and success criteria before proceeding with requirements activities.
Exam trap
The trap here is that candidates often jump to stakeholder analysis (Option C) as a first step, but the CAPM exam tests the sequence of business analysis planning: the business case must be validated before any requirements activities begin.
How to eliminate wrong answers
Option A is wrong because creating a requirements management plan is a process that follows after the business case is clarified; it does not address the missing problem statement and objectives. Option B is wrong because proceeding with requirements elicitation without clear objectives risks gathering irrelevant or conflicting requirements, wasting effort and increasing rework. Option C is wrong because stakeholder analysis identifies who to involve but does not directly resolve the missing problem statement and measurable objectives; the business case must be refined first to guide stakeholder engagement.